There should be no side effects if pre-loading is turned off.
The pre-loading is done, to improve the performance of JackRabbit requests for resources thats are stored in the database. Without the pre-loading, a simple property read results in about 300 database queries.
This is due to an inherent design issue with JackRabbit since the data is not structured ideally for storing in a relational database.
From an end user standpoint, without the pre-loading you will notice that the built-in CMS Admin tool is significantly slow
Could you tell how to turn it off please?
I am also interested in how to turn it off.
or tune it.
I will look also if there is something about that in the documentation...
may be write a wiki about the cache management in the cms ?