There are a couple of things to keep in mind when you're facing speed issues with PlanSwift.
PlanSwift in its current form is a 32-bit application, so it will have a limit on how much RAM it can actually use. Windows will cap PlanSwift at 2 gigs of RAM usage. When it starts to get close to its cap, it can bog down and can crash. A couple of things can help with this:
1. Having at least 4 to 6 gigs of RAM; 4 gigs is the minimum we recommend.
2. The more applications you have running alongside PlanSwift, the more RAM that is being used, and the more likely you are to run into a situation where PlanSwift bogs down. So shut down any unnecessary programs that may be running alongside PlanSwift to minimize the RAM usage as much as possible.
3. The more data you have inside of PlanSwift, the more RAM PlanSwift is going to use, so closing PlanSwift when you start to see it running slowly, should help to alleviate some of the slowness you're encountering.
4. If you are working from a network location, the communication between PlanSwift and that network location will cause PlanSwift to slow down. To alleviate speed issues, you can move the job to your local drive, work on the job, and then move it back.
5. If PlanSwift is taking a long time to launch, or fully load when launching, you can go into your Settings, select General, and uncheck the box for Automatically open the last job when PlanSwift opens. This will help PlanSwift to launch a little bit quicker.
6. DPI issues such as having too high of a DPI setting for images or using PDF files with very high DPI settings can also slow down PlanSwift. Click here for how to resolve DPI issues.