Excessive Heap Memory Usage in SharedTree Compared to PropertyDDS #25696
Description
Describe the bug
We are observing an issue in production environment where excessive heap memory usage with SharedTree is leading to application crashes.
As part of our investigation, we compared the memory utilization of SharedTree and PropertyDDS while loading the same container. The results indicate that SharedTree consumes significantly more heap memory—approximately 20x higher—than PropertyDDS under identical conditions.
| Framework | Stage | RSS (MB) | HeapTotal (MB) | HeapUsed (MB) |
|---|---|---|---|---|
| PropertyDDS | Before loading | 490 | 109 | 63 |
| PropertyDDS | After loading | 494 | 111 | 72 |
| SharedTree | Before loading | 448 | 65 | 62 |
| SharedTree | After loading | 663 | 270 | 235 |
Observations
- SharedTree shows a large heap increase (~173 MB) after container load compared to only ~9 MB with PropertyDDS.
- The same schema and data set were used in both cases.
- We have also tried using ForestTypeOptimized, but it did not result in any noticeable memory improvements.
- Schemas are created dynamically and typically include combinations of arrays, maps, and strings.