Open artem-tim opened 1 year ago
Hey @artem-tim, sorry just noticed your request.
This can be related to max children limitation, if the variability of the child keys are two high (there is no pattern) it will stop recording children on each level after 10 of them. You can increase that limit by passing
--maxChildren=100
with any arbitrary number, though with higher numbers the tool will consume more RAM when running.
Summing the consumption of root level keys of the table output only adds up to about 60% of the total in my case (of about 1.5GB). The same result with the chart, where about 40% is blank. Any idea why that's happening ?