My agenda view processes many items with
DEADLINE fields, and fully generates from scratch in about 0.3s. However, if I append
CUSTOM_SCHEDULED<"<now>" to my agenda view definition, the same view takes 2.1s to generate. How can I add a custom time-like property in a way that does not wreck the performance of the view?
- org-tags-view 904 97% - org-scan-tags 888 95% - #<lambda 0x5be5aafca262231> 838 90% - and 838 90% - progn 838 90% - or 837 90% - and 835 89% - not 835 89% - org-time< 833 89% - or 831 89% - org-cached-entry-get 831 89% - org-entry-properties 822 88%
As you can see, there is an explicit
org-time< call that is causing the slowdown. What's interesting is that
DEADLINE properties appear to use some other mechanism, since they do not cause the same hot loop in