https://bz.apache.org/bugzilla/show_bug.cgi?id=59258
--- Comment #7 from Philippe Mouawad <[email protected]> --- (In reply to Sebb from comment #6) > (In reply to Philippe Mouawad from comment #5) > > (In reply to Sebb from comment #4) > > > I think Vladimir means that removal of the first element of those data > > > structures is an expensive operation. > > > > Ok I agree > > > > > > > > Therefore the 'cure' might cause other problems. > > > > > > As to the solution, my preference is to not try to fix it through code. > > > > What do you propose then ? > > Continue with education. Unfortunately, I am not sure it's enough. > > > > > > > However of course it would be quite cheap to start dropping entries when a > > > limit is reached. > > > > Isn't it what my patch does ? > > If it's cheap , then why not do it this way ? > > Sorry, meant to write 'samples' not 'entries' - i.e. don't add another entry > if the list is full. That should be cheap and solves the OOM. Yes that's another way to fix it. But if you take a long running test: - I suppose user would be more interested in last samples than old ones - He might think JMeter is stuck, which ends up the same from User perception : "JMeter is unstable, my test is stuck ...." -- You are receiving this mail because: You are the assignee for the bug.
