Hi Chris,
I often see that MWServer demands very high CPU% (from ~100% up to 300%) after I ran Variation 6 Experiments several times. It runs modestly (< 40 CPU%) initially, but I guess it starts to peak after the first block finishes (perhaps related to image loading/unloading? — although I’m not 100% sure…). Could you look into this please?
Thanks!
Ha
Hi Ha,
As you noted offline, the high CPU usage starts after closing an event stream file (regardless of whether you run your experiment). I’ve identified the cause of the problem, and the fix should be in tonight’s nightly build. In the meantime, there’s really no way to avoid the issue. Once MWServer gets in to the bad state, your only option is to quit and re-launch it.
Cheers,
Chris