Optimize purview query for getting features #584
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Resolves #564
Input
start = time.time()
features = registry.get_project_features("enya_test_registry")
feature_list=list([to_camel(e.to_dict()) for e in features])
print("duration1: ", time.time()-start)
start = time.time()
features = registry.get_project_features_origin("enya_test_registry")
feature_list=list([to_camel(e.to_dict()) for e in features])
print("duration2: ", time.time()-start)
Output:
duration1: 2.2548649311065674
duration2: 16.783140897750854
How was this PR tested?
Does this PR introduce any user-facing changes?