Performance

1. Why does the model take 2 minutes to start up?
2. Why does the model take half an hour to start up?
3. Why doesn't the model start up?
4. How can I make the model run faster?
5. What minimum RAM and processing speed would you recommend for our large coverages to run best?
6. The ProximalTopology tool quit after lengthy processing. What's up?
7. How do I add extra command options with the new Application Launcher, like this extra java option: -Dsun.java2d.d3d=false?

1.

Why does the model take 2 minutes to start up?

The Patchworks model performs a substantial amount of work when it first starts up to read in data files and initialize program control structures. Five minutes is not an unusual amount of time for the start up process.

2.

Why does the model take half an hour to start up?

Under normal circumstances Patchworks should not take more than 2 minutes to load and prepare for execution. There are several reasons why the model might take an unusually long time to load:

  • Patchworks may take a long time to start up if the datasets are located on optical media or if they are stored on a remote file-server. To ensure best performance it is a good idea to store all of the data files on a local hard disk within your workstation.

  • Patchworks may take an exceptionally long time to load and will perform very poorly if your workstation is equipped with insufficient RAM. In our experience small models require a minimum of 512Mb of RAM, and medium sized models require 2Gb or greater. Problem size is difficult to describe in simple terms, but is related to the number of block polygons, the complexity of the growth and yield database, and the type and number of spatial design objectives.

3.

Why doesn't the model start up?

If you are having problems getting the software to operate try the following trouble-shooting checklist:

  • Check the amount of available RAM. Open the 'System' icon in the control panel. The amount of installed RAM is listed under the heading of 'Computer'. Make sure that you have sufficient RAM for the problem that you are trying to load.

  • Check the version of Java that you are using. To do this open a 'Command Prompt' window, and type in the command java -version. If Java is installed correctly it will report that it is running version 1.8 or higher.

  • Check that the hardware security key is inserted in the USB port, or that you have correctly enabled the floating license option.

  • If you have just installed Patchworks for the first time then you will need to reboot the computer.

4.

How can I make the model run faster?

We have tuned the Patchworks model to achieve the best performance possible. The speed at which the model will converge on solutions depends on characteristics of the input datasets and objectives that you have set. Some features of the Patchworks model take more resources than others. You should be aware of the following issues:

  • Patchworks uses CPU resources to update the mapview while the optimizer is running. If you disable the mapview (by unchecking the active themes) these resources will be available to solve the problem faster.

  • Patchworks uses substantial memory and CPU resources to track patch constraints and to develop road access networks. You can speed up convergence by removing unnecessary patch and road modeling accounts. (You will need to restart the model to make these changes take effect.)

5.

What minimum RAM and processing speed would you recommend for our large coverages to run best?

The single most demanding requirement of Patchworks is RAM. For large problems we use a 64-bit operating system (Windows 10 Pro 64-bit) and up to 32Gb of ram. Note that on a 32-bit operating system the Java environment cannot make use of more than 1.5Gb of ram.

However, your memory requirements will depend on your planning problem. Many planning problems that we have looked at fit in under 1Gb. What makes the problem size grow is

  • lots of complicated succession rules and silvicultural treatments

  • lots of habitat, seral stage, cover type etc attribute curves

  • road network modelling

  • patch size modelling

  • a large number of polygons

If you plan on doing all of the above then 2Gb should be considered your lower limit.

The Patchworks algorithms run on multiple threads of execution, and will make use of multiple cores if available.

6.

The ProximalTopology tool quit after lengthy processing. What's up?

The program probably ran out of memory. You will need to provide it with at least 200Mb of Virtual Memory, and possibly more depending on the dataset size and raster resolution.

7.

How do I add extra command options with the new Application Launcher, like this extra java option: -Dsun.java2d.d3d=false?

Patchworks maintains a file named "patchworks.ini" in your default home directory (usually under c:\Documents and Settings\your_name\pathworks.ini), which contains settings that are remembered from one run to the next. Many of the lines in the file are the individual settings for the wizards that start the Patchworks programs.

The line having the keyword 'patchworks.javaflags' specifies additional java command lines arguments that are to be used for every command started from the Application Launcher. You can add or edit this line to include additional java arguments, such as

patchworks.javaflags=-Dsun.java2d.d3d\=false