From 2.9 b665: fixed timeout errors with large files.

From 2.9 b667: several seconds shaved from load-time for certain large files

From 2.9 b663: persistent server-side caching of data requests.

A data request happens when the browser needs to query the server, such as upon changing tabs, filtering or selecting in the browser.
Mobile already caches data requests in spare memory, meaning the same action is near-instantaneous (bandwidth permitting) when repeated by another user.

This change means that routine server restarts don't lose the cache. (However if the server version is upgraded, clearing the cache is unavoidable.)

2.9 b668: new advanced Mobile Web Server option to keep specific files loaded into memory at all times, effectively ring-fencing server memory.

This ensures that large files are available for immediate interaction, even after restart or extended periods of disuse/inactivity, but requires the administrator to ensure the total number of matching files doesn't incur more memory requirement than is available in the system and allocated to the server.

In the configuration UI, the option "Keep-loaded pattern" accepts one Ant-style wildcard, such as "a/**/b*c.iok" where "**" matches any number of folder levels including none, and "*" matches any sequence within a filename.
In the XML, this option is shown here:
... <mobilewebserver ... keepLoadedPattern="**/Bond prices.iok" ... > ...
Multiple patterns can be specified, comma-separated.

You might configure this if you have:
- only one file
- several files, but only one is performance critical (e.g. used in a key demo)
- several files, and all fit into server memory
(for example).

To some extent, this option is a stop-gap until planned major improvements to the scalability of the data engine in Omniscope Mobile.

Read on...

2.9 b669: new Mobile Web Server option to preload specific files on server startup.

This is a safer, less advanced cousin of "keep-loaded pattern" above. It allows you to configure frequently used files so they are more immediately responsive after restart. However, a period of inactivity or intensive use with other large files may cause these files to be subsequently unloaded.

In the config UI, the option "Preload-on-start pattern" accepts an Ant-style wildcard as above.
In the XML:
... <mobilewebserver ... preloadOnStartPattern="**/*xyz*.iok" ... > ...

You can use this more freely than "keep-loaded pattern", since it can't overload the server's memory. You might use this to preload files which are commonly used, larger, or performance critical.

With both "preload-on-start pattern" and "keep-loaded pattern", view the log to check your configuration is correct. This is typically served at:
https://localhost:48443/logs/mobilewebserver
or found on disk at:
C:\Users\USERNAME\omniscope-server\logs\service_mobilewebserver_log.txt (Windows)
~/omniscope-server/logs/service_mobilewebserver_log.txt (Linux)
With entries such as:
2013-11-27T09:12:24.161+0000 INFO [omniscope.service.mobilewebserver.server] - Preloading: E:\Scratch\Bond prices.iok
2013-11-27T09:12:24.346+0000 INFO [omniscope.service.mobilewebserver.server] - Preloaded: E:\Scratch\Bond prices.iok