When running FDTD simulations on a local desktop, the default setting is to use the maximum number of cores in the system. Depending on your simulation, this might run slower using all cores/processors. This page shows how to determine the optimum resource configuration to run your FDTD simulations. This will also come handy as a baseline when requesting for resources on the cluster to run your simulation job.
Check Simulation Memory Requirements
- Open the simulation/project.
- Check your simulation memory requirements.
- Make sure that you have enough RAM/Memory installed on your machine to run the simulation.
If your simulation requires more than the memory installed on your machine, expect the simulation to run slow since it will use your virtual memory (hard drive) to run your simulation. Otherwise, modify your simulation to lower the memory requirements or run the simulation on a different computer with sufficient memory.
Run Simulation With Different Resource Settings
- Open Resources.
- Set Processes to about half of the number of cores on your computer, keeping Threads to 1. i.e. on a 24 core or more machine, 6 or 8 processes would be a good starting point.
- Save and run your simulation.
- When the Status in the Job Manager indicates the simulation is done initializing and meshing and it is in the "Running" state, click Quit & save.
- A log file will be created for your simulation,
[filename]_p0.login the same folder as your simulation file. Open the log file with a text editor. At the end of the file, it will indicate the FDTD solver speed inMnodes/s.
- Repeat the process and run your simulation while increasing the number of Processes, taking note of the solver speed for each run, until you are using the maximum available cores on your machine. e.g. 12, 18, 24, etc... (always even number).
Based on the results on the simulation log file, use the number of processes that provided the best performance (i.e. highest Mnodes/s).
Note: The number of processes will depend on your simulation and hardware and could vary for each simulation and computer that will run the simulation.