Memory Cache will not help the First Time per session load time and if you are okay with the performance after the first time, don’t use the Memory Caching.
There are two settings that can help and they are in the Client Sysconfig file. They are:
<MaxBOMRU value="100" />
<MaxClssAttrMRU value="20" />
I suggest that you set the first in the 80 to 100 range and the second around 50 (20 is probably too low for most users).
The Client uses those settings to “tune itself” so that BO Security settings and Dataset Extended Property settings are loaded in one call while the Menu loads. Using the settings above, one call would be made to get BO Security for 100 BOs and one call would be made to get the Extended Props for 20 datasets. That data is then loaded into the Client Memory so that it does not have to fetched from the Server again. If that data is not already in memory, it is loaded one by one during the first load of a form. If a form References 10 Business Objects (not that unusual) ten separate requests for the Security information for each BO would be made while the form loads and the same is true for the different Datasets referenced on the UI.
The list of which BOs and which Datasets are commonly referenced by a user is maintained in the Client Disk Cache and it is written out as the Client process terminates so upping the numbers will not have an immediate effect. The user needs to run for awhile, logout, and then on the next login - assuming no one cleared the cache - Menu load should be slower but first time form load should be faster for the commonly used forms.
In playing with this I see that we are not properly utilizing the Client Cache for the Customization and Personalization layering so I will have that reviewed but in the meantime, try upping the numbers on the settings above.
BTW - those settings (and many others) are discussed at Insights in the “Client Internals” sessions. I believe “early bird” pricing is still available…