Ihor Radchenko writes: > > However, please move the obsolete function definition to org-compat > instead of removing it completely. We do it to avoid unexpected breakage > for people and libraries who happen to use this public function. Done. See attached > 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. 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. org-cached-entry-get 1st run: 26.868990287 2nd run: 16.043983143 org-entry-get 1st run: 18.209056578 2nd run: 5.003186764