Another tiny problem I’ve noticed when running scenarios in AWW environment is the “stuck” issue. After I start a run, if I want to generate a new input scenario/make edits to an input parameter/etc. immediately, the OpenM++ system would then be responding very slowly and feels like it’s stuck. If I wait until that run is complete, then everything becomes smooth again. My guess is that the CPU/server is fully occupied when the run is working, We don’t have this problem with Steve and Anatoly’s cloud version, so wonder if it’s something that could be improved.
Duplication and no longer relevant as the new architecture of Microsimulation services on AAW will be completely different from when this was reported.
Describe the bug
Another tiny problem I’ve noticed when running scenarios in AWW environment is the “stuck” issue. After I start a run, if I want to generate a new input scenario/make edits to an input parameter/etc. immediately, the OpenM++ system would then be responding very slowly and feels like it’s stuck. If I wait until that run is complete, then everything becomes smooth again. My guess is that the CPU/server is fully occupied when the run is working, We don’t have this problem with Steve and Anatoly’s cloud version, so wonder if it’s something that could be improved.