2013-03-19, 23:25:49
It can be more complex, you can query any thing you can imagine in microseconds, and manage it all seperatly. With a file based backend you have to consider how to efficiently load all those files and create caches of the fields you need.
Say I want every tag of every file, for searching perhaps, I have to load every file and extract the tags. This can hit memory and time limits. So i wuold have to know in advance and do this once and craete a cache of these tags, but then what if i want some other metric I have to plan that also.
With gs we have a pagecache that holds everything for all pages except the content fields, so we can load 1 file and access all the metrics for the pages. It gets updated routinely when stuff changes.
I have a test site I use with 2000 pages of full content and metas, and the cache file it generates is only 1 mb and loads almost instantly.
But the issue it has is 2 fold, the menu sorting has not been updated for caching causing delays on the backend and the pages viewer cannot accomodate all these efficiently, it is one giant list.
Oh and FYI 3.2.1 + loads pagecache on the front end always, at least for now.
Say I want every tag of every file, for searching perhaps, I have to load every file and extract the tags. This can hit memory and time limits. So i wuold have to know in advance and do this once and craete a cache of these tags, but then what if i want some other metric I have to plan that also.
With gs we have a pagecache that holds everything for all pages except the content fields, so we can load 1 file and access all the metrics for the pages. It gets updated routinely when stuff changes.
I have a test site I use with 2000 pages of full content and metas, and the cache file it generates is only 1 mb and loads almost instantly.
But the issue it has is 2 fold, the menu sorting has not been updated for caching causing delays on the backend and the pages viewer cannot accomodate all these efficiently, it is one giant list.
Oh and FYI 3.2.1 + loads pagecache on the front end always, at least for now.