Intelli-Cache Options#

I was thinking why not give the user the option to choose which resource caching method to use for every resource in the system?

This is how it would work:

On every resource screen give users a Cache Method option. This would be a drop-down box with three options:

1) In-Memory
2) On disk isolated
3) On disk collective

The "in memory" option will allow the resource to be also cached in memory (as is now). The "On disk isolated" option will allow the reource to be cached in a separate file. While the "on disk collective" will allow reources to be cache according to the group or category they belong to. For exmaple plugins could be grouped by events will snippets etc will be grouped by categories, etc.

Is some cased it would be necessary to store cache in memory in other cases it would not. IMO these options will allow the site admin to optimize the performance of his website based on the about of apps loaded and user load.

A system configuration option can be added to allow the user to choose the default method to use. IMO we could use 2) "On disk isolated" as system default since it's more scalable with user loads.

What do you think?

I was thinking why not give the user the option to choose which resource caching method to use for every resource in the system?

This is how it would work:

On every resource screen give users a Cache Method option. This would be a drop-down box with three options:

1) In-Memory
2) On disk isolated
3) On disk collective

The "in memory" option will allow the resource to be also cached in memory (as is now). The "On disk isolated" option will allow the reource to be cached in a separate file. While the "on disk collective" will allow reources to be cache according to the group or category they belong to. For exmaple plugins could be grouped by events will snippets etc will be grouped by categories, etc.

Is some cased it would be necessary to store cache in memory in other cases it would not. IMO these options will allow the site admin to optimize the performance of his website based on the about of apps loaded and user load.

A system configuration option can be added to allow the user to choose the default method to use. IMO we could use 2) "On disk isolated" as system default since it's more scalable with user loads.

What do you think?

Great plan Raymond -- this is similar to a J2EE object caching system I used in a recent gig with a call-center application -- the flexibility and ease of updating individual or logically grouped sets of objects in cache was very cool. I'm assuming there would also be individual controls for updating cache objects or collectives?

Great plan Raymond -- this is similar to a J2EE object caching system I used in a recent gig with a call-center application -- the flexibility and ease of updating individual or logically grouped sets of objects in cache was very cool. ?I'm assuming there would also be individual controls for updating cache objects or collectives?

Yes this can also be implemented. If a resource is cached separately then it can update its own cache file or force a group update.

Another thing that can be worked on is the way how cache files are being executed. Travis made some mention of this some time ago. I think I might have found a way how to make the system execute snippets, plugins, tvs faster even with hundereds on a page.

Since it looks like the last of the major features are now being committed as we speak, time to resurrect this topic. I think an improved caching system that does the above and also automatically handles snippets properly would be a big improvment.