Hi, @KK
It is beneficial for correctly set up MySQL server to cache database requests. But since couch has a seconds precision for publish date, caching such requests is not optimal. Instead, memory cache is filled with thousands of such trash (1) and more energy is wasted to find the same result set over and over again (2).
If publish date could be set with precision 'hour' then ideally during the whole hour, cache will be really helpful for websites with many visitors. 'show_future_entries' does not help to overcome, because the feature is lost and people use this to set publication date for tomorrow or in a week.
I don't see how seconds are ever needed in such situations. Nobody sets publication for tomorrow, 12h 01m 38s.
It is beneficial for correctly set up MySQL server to cache database requests. But since couch has a seconds precision for publish date, caching such requests is not optimal. Instead, memory cache is filled with thousands of such trash (1) and more energy is wasted to find the same result set over and over again (2).
If publish date could be set with precision 'hour' then ideally during the whole hour, cache will be really helpful for websites with many visitors. 'show_future_entries' does not help to overcome, because the feature is lost and people use this to set publication date for tomorrow or in a week.
I don't see how seconds are ever needed in such situations. Nobody sets publication for tomorrow, 12h 01m 38s.