[Ready-to-review] Adding caching to PyPerfNativeStackTrace #421
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.
Resolving the issue #379
1. Summary of changes
2. Results [this section will be updated soon]
Methodology:
while 1: pass
) were running for all this time3. Screenshot for the scenario with official docker image (granulate/gprofiler:1.6.0)
3.1.


_Ux86_64_get_proc_name
matches3.2.
_Ux86_64_get_proc_name
matches for filteredPyperf
process4. Screenshots for the scenario with enabled caching in PyPerfNativeStack
4.1.




_Ux86_64_get_proc_name
matches4.2.
_Ux86_64_get_proc_name
matches for filteredPyperf
process4.3.
cache_exiction
matches4.4.
cache_exiction
matches for filteredPyperf
process5. Comparison
Before (docker image granulate/gprofiler:1.6.0):

After enabling caching
