<quote>The decision to cache or not should be made by a sysadmin</quote>
I agree. This should be a configuration aspect. But I would suggest to have it by default set to false. We have to take into consideration that in testing and staging environments the data sets to work with can be limited in size as compared to the production environment. And performance measurements might go unnoticed. Having it set to false by default, can also build merit for the system integrator/system admin when he switches the caching configuration from false to true to improve performance (perception). When done with true by default and done the other way around, I expect that yielding the same result might prove more difficult. Best regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Sat, Mar 21, 2015 at 11:22 AM, Adrian Crum < [email protected]> wrote: > I will try to say it again, but differently. > > If I am a developer, I am not aware of the subtleties of caching various > entities. Entity cache settings will be determined during staging. So, I > write my code as if everything will be cached - leaving the door open for a > sysadmin to configure caching during staging. > > During staging, a sysadmin can start off with caching disabled, and then > switch on caching for various entities while performance tests are being > run. After some time, the sysadmin will have cache settings that provide > optimal throughput. Does that mean ALL entities are cached? No, only the > ones that need to be. > > The point I'm trying to make is this: The decision to cache or not should > be made by a sysadmin, not by a developer. > > Adrian Crum > Sandglass Software > www.sandglass-software.com >
