There are few things that may cause Voxler to run slowly. To speed up Voxler:
- Make sure your OpenGL driver is hardware accelerated.
The drivers that come from Microsoft are usually NOT accelerated, while the drivers that come from the hardware manufacturer usually ARE accelerated.
- Make sure hardware acceleration is enabled
Hardware acceleration can be found in Tools | Options | General | Enable Hardware Acceleration. Note that you must restart Voxler for this setting to take effect.
- Set View | Transparency Type to Blend
Some of the higher quality transparency modes can greatly slow down rendering. Blend offers the best performance.
- Reboot the computer.
The computer may have enough free available memory to perform the desired operation(s), but if it is fragmented over several blocks, then Voxler can only use the largest block of memory available. If you believe you have enough RAM, reboot the computer to defragment the memory, close down as many running applications as possible, and then try the operation(s) again.
- Click Tools | Options and on the General page, set the Undo Levels to 0.
Voxler may be holding memory for the number of Undo levels you have set. If you have the number of Undo levels set to 15, then Voxler has to hold the necessary memory to be able to undo the previous 15 actions. If they are actions that take a lot of memory, then Voxler has to hold onto the same amount of memory it took to perform the actions so it can undo them. Restarting Voxler resets the Undo actions so Voxler can release the memory it was holding. Another option is to set the number of Undo levels to 0 or some other smaller number, so Voxler can release some more memory.
- Try the 64-bit version of Surfer on a 64-bit operating system.
The 64-bit version allows for more memory to be available for Voxler.
- Turn off Auto Update
If you have a lot of graphics in your project and you're trying to perform actions that change those graphics, it can bog down your machine. To get around this, uncheck the Auto Update checkbox at the top of the Property Manager during edits, and then turn it back on when you're all done making changes.
- Reduce the amount of required memory
If there is a lot of hard disk activity and everything seems extremely slow, then your computer may have run out of memory and is trying to page to disk. Voxler requires all network data and graphics output to reside in memory. Several steps can be taken to reduce the amount of required memory:
- Use the Subset module to extract a portion of large lattices, save the extracted data to disk, and use the saved file in future runs.
- Use the ChangeType module to change the data type of large datasets to one that requires fewer bytes.
- Avoid graphics that require large amounts of memory like VolRender modules.
Updated August 20, 2018