Friday, March 23, 2007, 9:08:04 PM, you wrote: >>> No, but I use my little modification which actually gets rid of >>> the BeanShellScripts cache. This is a real turn-off with no >>> overhead. Currently hardwired, but with a little more coding >>> it could easily be controlled via properties, if needed. Could >>> be applied to all caches not just BeanShellScripts. >> >> This might be interesting. Would you consider to open a Jira issue for >> this ?
> Why would we want to do this? > The main reason I consider a cache timeout to be an adequate disable > mechanism is that the performance overhead for maintain the cache is > NOTHING compared to the performance impact of having the cache > disabled (maybe 1000:1, perhaps 100,000:1 for reloading and parsing a > BSH script). I think all this boils down to the following: - In either production or development we should always use cache for performance, but with adequately large expiration time in order to avoid the overhead. - In development we can simulate turning off with setting expiration time to an extremely low level with a tradeoff - To turn off the cache entirely implementing a new feature would be needed (would also help later to decide whether a certain problem is cache related or not) So far it is only me who is not happy with the workaround. Jacques might also find this idea useful. I think it's up to the ofbiz community to decide, whether a real turn off of cacheing feature is needed or not. Please let me know how the community decides about this (vote/jira etc). Thanks, András > -David
