CAndCPlusPlusProfilingResults
Profiler Results
CPU Profiling
Monitor Profiling
- All blocks statistics
- Parsers blocked by access to different shared resources Parser 0, Parser 1, Parser 2, Parser 3
- Parsers blocked by access to shared strings contaner Several parser threads most time spent on sharing concurrent string manager resource
- Parser blocked by AWT thread In this stack we can see, that when new file buffer is created it can be blocked by the lock used at the same time from AWT thread. The reason is the search of DataObject for FileObject which cause full Data/File Objects resolving cycle. This is very rare situation and can be postponed.
Memory Profiling
- There is a big empty table field in WeakSharedSet.m.table, but this is OK
Attachments
- Media:Monitor-Parser-1_CAndCPlusPlusProfilingResults.html
- Media:Monitor-Parser-2_CAndCPlusPlusProfilingResults.html
- Media:Monitor-1_CAndCPlusPlusProfilingResults.html
- Media:Monitor-Parser-0_CAndCPlusPlusProfilingResults.html
- Media:Monitor-2_CAndCPlusPlusProfilingResults.html
- Media:Monitor-Parser-3_CAndCPlusPlusProfilingResults.html

