The default sample Dump CRD includes a thread dump and a heap dump. Although a thread dump is very lightweight (generally pauses the JVM for less than a few hundred milliseconds and only consumes a few MB of disk space) and commonly useful (includes thread dumps, configuration, lock contention, environment variables, etc.), a heapdump PHD file is much heavier weight (generally pauses the JVM for up to dozens of seconds for realistic production workloads and consumes up to hundreds of MB of disk space) and is much less commonly useful (a PHD is automatically created for an OutOfMemoryError so manual PHDs are generally reserved for advanced tuning and sizing of Java heaps). Therefore, PHDs are not generally recommended except for rare uses cases where they are needed. For reducing performance impact and disk usage for the most common use case of requesting a server dump, it's generally recommended not to request a heap dump (nor system dump).
The default sample Dump CRD includes a thread dump and a heap dump. Although a thread dump is very lightweight (generally pauses the JVM for less than a few hundred milliseconds and only consumes a few MB of disk space) and commonly useful (includes thread dumps, configuration, lock contention, environment variables, etc.), a heapdump PHD file is much heavier weight (generally pauses the JVM for up to dozens of seconds for realistic production workloads and consumes up to hundreds of MB of disk space) and is much less commonly useful (a PHD is automatically created for an
OutOfMemoryErrorso manual PHDs are generally reserved for advanced tuning and sizing of Java heaps). Therefore, PHDs are not generally recommended except for rare uses cases where they are needed. For reducing performance impact and disk usage for the most common use case of requesting a server dump, it's generally recommended not to request a heap dump (nor system dump).