Java Profiler Knowledge BaseTroubleshooting: working with the profilerMemory snapshot opens too slowlyCan't find your answer? Please refer to documentation and demos, ask your question in forum, or contact support.
Opening a big memory snapshot sometimes takes a lot of time. Usually it is normal due to the fact that some complex calculations are to be made by the profiler while loading the snapshot.
Still you can use the following solutions to make snapshot opening faster.
If possible, open big memory snapshots running the profiler UI on a 64-bit system. The reason is that snapshot opening is a memory hungry operation, thus you would benefit from 64-bit processing capabilities.
In any case while loading the snapshots, try to avoid simultaneous running of other applications which use much memory. Running several applications may cause active disk swapping that leads to overall system performance degradation.
Since version 8.0, YourKit Java Profiler provides an ability to save memory snapshot index.
When a snapshot is loaded for the first time the profiler can store some pre-calculated information, the snapshot index, to a file alongside the original snapshot. The snapshot index will make the next snapshot opening much faster.
The snapshot index files may be helpful in analyzing big snapshots on a 32-bit workstation. The index files can be generated on a 64-bit server, manually or programmatically, and then transferred back to your workstation.
Please read Saving memory snapshot index help topic for detail.