Morgan Smith <morgan.j.sm...@outlook.com> writes: >> Also, with the old approach, if you observe slowdowns, you likely have >> some property being calculated slowly (like BLOCKED in my case). Do you >> happen to know which property is it for your setup? > > According to my profiler, I think it's using 30% of the CPU time during > my custom org-clock-sum just to get ITEM. I suppose it's because it > thinks it has to grab and cache everything when all I'm after is ITEM.
Not sure here. Getting ITEM is just a single regexp match. May you share the profiler report? (M-x profiler-report-write-profile) > I don't see anything else that looks suspicious in the profiler so I > suspect you're seeing a much worse case then I am. I'll copy paste my > previous performance numbers here again just so you can see my slowdown > is only between 1.5x and 3x. In my case it was more like 10x :) > * lisp/org.el (org-make-tags-matcher): Replace uses of > `org-cached-entry-get' with `org-entry-get'. > (org-cached-entry-get): Move to ... > * lisp/org-compat.el (org-cached-entry-get): ... here. Obsolete in > favor of `org-entry-get'. Applied, onto main, after adding missing declare statements to pacify the compiler. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=646f6ec13 -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
