Eric S Fraga <e.fr...@ucl.ac.uk> writes: > 832,940,181 99% - command-execute > 805,535,710 96% - funcall-interactively > 540,874,166 64% - gnus-summary-exit > 537,712,423 64% - gnus-score-save > 536,634,533 64% - gnus-pp > [...] > > It could be that I am misinterpreting those profiler results.
I think so, yes. These numbers cannot be interpreted directly as used memory. It's more like "time spent inside the function, measured memory-usage wise. > I tried this as well and also get results immediately. Hmm. Ok. We could try with M-x trace-function pp-to-string RET directly before `gnus-summary-exit'. A popup buffer should appear, and it would be helpful if you could again post the output (with any private data obfuscated; we are interested in the argument(s) of the function call(s)). But before that please M-x untrace-all RET. > > Have you tried to change the value of `pp-default-function' btw? > > No, it's set to pp-fill. Are things significantly faster when setting this to pp-28? Thx, Michael.