When working with a map component containing "many" images in Future, my system freezes briefly while drawing the component on screen.
My system is a Dell XPS laptop with a Kaby Lake i7 2.8ghz cpu, 32gb of RAM and a geforce GTX1050 gpu. I am suspicious that this specific CPU's "stutter" problem may be the culprit, and wonder if anyone else sees the same behaviour in their non-Kaby-Lake systems.
Here is the scenario, and my thanks in advance for any troubleshooting recommendations.
I have a v9 map file that is ~15gb in size. It was created by opening a v8 map file in Future 220.127.116.11, then "Saving As". The map file is stored on the local SSD of this same machine on which I am running Future.
The map file contains 68 image components. Each are 128x128 tiled, uint8x3 tile type, and about 7000 x 8500 pixels in size. They are all projected in EPSG 3578.
I have a map component which is assigned as EPSG 3578. That map component has about 30 of the images as item entities.
When I double click the map component to "open" it, the mouse cursor freezes on screen for about 10 seconds. Task manager shows a spike in CPU usage (see attached), but no other resource use changes (disk, ram remain same). After 5 seconds or so, the map displays correctly and control is returned.
Subsequently panning the map produces that same behaviour; a complete freeze of the system with a spike in CPU usage, lasting about 3-5 seconds. Pressing the "windows" key on my keyboard during that "freeze" does not open the Windows Start menu until after the map window has drawn.
In the original Release 8 map file, loaded in 18.104.22.168 x64 on this same machine, the same map component snaps open immediately, and all images are drawn immediately with system control retained. Pans, zooms, etc, are all fast and fluid.
It may be the case that there is some issue with this particular hardware configuration, in which case I would love to know!
Thank you for an advice you can offer.