On 2025-12-26 21:10, Ihor Radchenko wrote:
pinmacs <[email protected]> writes:
Since long time, I was wanting to have how much time it takes to render
any org-agenda view. Because when it takes too much time, then I should
spend time on archiving parts of my content that could be processed by
the org-agenda-files.
Why not simply M-x profiler-start and go from there?
I feel profiler-start is more when you are developing, improving or
evaluating emacs lisp, . In fact, it is more focused on measuring cpu
and memory, no?
But when you are looking at your org-agenda, you just want to know what
should be done today, etc. Which is similar when in some services you do
a search or get a page and in the footer you encounter how much time it
took to serve the content, that's why I feel is natural and lightweight
to just measure the time.
In fact, doing a simple demo, how can I easily extract the info and put
in a way that briefly informs the user? profiler-report is thought to be
used interactively
(profiler-start 'cpu+mem)
(sit-for 1.2)
(profiler-stop)
