Salesforce Apex debug log analyzer for Visual Studio Code - Visualize code execution via a Flame chart and identify performance and SOQL/DML problems via Method and Database analysis
This is more accurate but will not show an accurate number until we change the logic to sum unique paths in the stack.
Filtering could easily break this.
For example filter by namespace and now the only two methods in the analysis are siblings
Method 1 in pkg1 calls to Method2 and Method 3 in pkg2
Filter by pkg2 and both Method2 and Method3 should be included in the total with this change only the largest will be.
There will be a follow fix to be accurate
Type of change (check all applicable)
[X] 🐛 Bug fix
[ ] ✨ New feature
[ ] ♻️ Refactor
[ ] ⚡ Performance Improvement
[ ] 📝 Documentation
[ ] 🔧 Chore
[ ] 💥 Breaking change
[optional] Any images / gifs / video
Related Tickets & Documents
Related Issue #526
fixes #
resolves #
closes #
Added tests?
[ ] 👍 yes
[X] 🙅 no, not needed
[ ] 🙋 no, I need help
Added to documentation?
[ ] 🔖 README.md
[X] 🔖 CHANGELOG.md
[ ] 📖 help site
[ ] 🙅 not needed
[optional] Are there any post-deployment tasks we need to perform?
Description
Changes the TotalTime column to show max time.
This is more accurate but will not show an accurate number until we change the logic to sum unique paths in the stack. Filtering could easily break this.
For example filter by namespace and now the only two methods in the analysis are siblings Method 1 in pkg1 calls to Method2 and Method 3 in pkg2 Filter by pkg2 and both Method2 and Method3 should be included in the total with this change only the largest will be. There will be a follow fix to be accurate
Type of change (check all applicable)
[optional] Any images / gifs / video
Related Tickets & Documents
Related Issue #526 fixes # resolves # closes #
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?