GUI: Stress Test

[gtdang]

We need to do a GUI stress test to get a sense of the GUI's memory use.

@ntolley @jasmainak could you give us typical ranges for:

• tstop and dt
• Number of simulations run within a session

Perhaps a matrix for us to test would be helpful.

[ntolley]

For GUI use, users should keep dt=0.025 (the default value). We really just use it to speed up testing and debugging, but for science/research it should stay small to keep the simulations numerically accurate

Simulations tend to be 100-1000 ms, the most common being ~200 ms

It's rare that people run more than 10 trials, but in practice most people run 1 trial at a time

[ntolley]

I think it'd be sufficient to say the worst case is running 10 simulations (ntrials=10) that are 1000 ms

My guess is this won't blow up the RAM as I've run workloads like this on my very modest laptop, but exact profiling results would be useful to extrapolate these values

[gtdang]

I think it'd be sufficient to say the worst case is running 10 simulations (ntrials=10) that are 1000 ms

My guess is this won't blow up the RAM as I've run workloads like this on my very modest laptop, but exact profiling results would be useful to extrapolate these values

Hopefully it won't be too bad! It would be good to know what the limitations are. Especially if you encounter folks with an egregious number of browser tabs running.