Peter Lieven <p...@kamp.de> writes: > this struct is approx 75kB
32KiB on x86_64, almost entirely eaten by member stack. As Dan observed, we use many short-lived QmpInputVisitors. However, we should not be using many simultaneously. That would be necessary for 32KiB objects to have an impact on memory use. Are you sure these have an impact? Implementing a stack as "big enough" array can be wasteful. Implementing it as dynamically allocated list is differently wasteful. Saving several mallocs and frees can be worth "wasting" a few pages of memory for a short time.
