I’m trying to debug an issue that looks like fdtd-engine isn’t obeying the resource limits put in place for a simulation. I’m not a Lumerical user so I currently don’t know if this is a bug or if it’s just a misconfiguration on our end.
What I’m seeing is that even though a simulation is run using a fixed number of threads, at various points in the sim all CPUs seem to go to 100% for short blips. This obviously isn’t great on a shared cluster node.
What is going on here? Are there points in a sim where it does garbage collection or combines the output from the individual sims? Is there a config setting that can limit the number of cores that are consumed in whatever job is being run here?