Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Perf: Optimize GetNavigationSource(ODataPath) #1118

Closed
habbes opened this issue Dec 1, 2023 · 0 comments · Fixed by #1161
Closed

Perf: Optimize GetNavigationSource(ODataPath) #1118

habbes opened this issue Dec 1, 2023 · 0 comments · Fixed by #1161

Comments

@habbes
Copy link
Contributor

habbes commented Dec 1, 2023

The GetNavigationSource(ODataPath) is relatively expensive. Part of the cost is due to the fact that we rely on a custom path segment handler to determine the path.

Once we ship an ODL version that support indexing ODataPath, we can rewrite this method using a simple loop that reads the segments from the end until it find the appropriate one to determine the navigation source.

Related:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant