web ui uses a lot of mem and is quite sluggish at times

[sanga]

I haven't looked into this at all, but I thought I would note it anyway. I was running a large test last night and noticed the web ui getting very slow to react (as in several seconds of latency). A quick glance at chrome's task manager revealed that the locust tab had 1 gig of memory.

Any obvious reasons why that might happen (both the list of requests and especially the list of failures were quite long, but 1 gig still sounds a bit excessive to me)? Apologies for the vague bug, I'll add more info here when I run into this again and have more time to look into it.

[heyman]

I haven't seen problems with the web UI unless the request list or failure list has been extremely long. I guess there could be some memory leak. Did you try to reload the page, and if so, did it return to being reactive?

[sanga]

I think I tried reloading and I think it was still very slow (didn't check memory consumption in that case though). There were probably 50 requests and perhaps 100 or 200 failures in the lists. That's not small but I wouldn't call it very long either. I guess it's most reasonable for me to just try and repro the situation and dig a bit more

[heyman]

Ah, no, that doesn't sound too much at all. Would be great if you could check more details if it happens again. Perhaps also even restarting the browser and see if that solves it (or at least killing the tab if you're running Chrome).

[sanga]

There's probably not a lot of point in keeping this open for the sake of it => Closing. Will reopen should I be able to repro it/get some more concrete info/steps-to-repro