When opening an ICM network for the first time (i.e. no network files in the local files "Working" folder), the WDS reads through the database file in 4 kB chunks to retrieve the requested version of the network. This read process appears to be limited to a disk "queue depth" of 1 and is therefore very sensitive to drive latency. In a cloud environment, drive latency can be in single digit milliseconds. Therefore, the read process might achieve 400 x 4 kB = 1.6 MB per second. If the database file is large, it can take many minutes for the network to open. A similar process appears to take place when producing graphs or statistical reports from results files. Would it be possible to re-engineer the database read process so that a larger queue depth or i/o size could be used to achieve a significant improvement in read times?
Thanks for this feature request. Although we haven't improved the performance of opening a network for the first time yet, in the 2024.4 update, we have provided a new result format option to improve performance of graphs and statistical reports. Hope this helps!