Why does EMIS hold when I first load the OneLauncher?

Why does EMIS hold when I first load the OneLauncher?

Some users may experience a pause when they load the OneLaunchers for the first time after logging into EMIS Web.

Our development team have noted that when loading the OneLauncher for the first time (each day) after logging into EMIS Web, it hangs for a while before loading. However, after this has loaded once, the OneLauncher and resources within them are loading much quicker than before. Overall, this should result in improved performance and better stability of EMIS.  We believe this is due to a recent release (9.13.10.0000) of EMIS which has improved the performance of resource publisher considerably, as this has only been noted since this update.  We would suggest users load their OneLaunchers soon after starting EMIS in the morning, then every subsequent load (when you're seeing patients and wanting to be fast) will be much faster.
EMIS Web has released an update (9.13.10.0000) with performance enhancements which has improved usual speed of load, but causes a delay on the first load of the day
The 9.13.10.0000 update in Resource publisher has improved the speed of retrieving data. 

There is an article on EMIS Now which mentions a performance enhancement relating to the SQLite Database:
To improve the syncing process between RP and EMIS Web we have migrated resources to an alternative Database, called SQLite. This will improve the caching mechanisms which are used to increase the speed of retrieving data. Overall improvements for this feature will reduce memory usage, and also improve system performance in EMIS Web.
You can read further details about this update here.