On 18 January 2012 20:37, Philippe Mouawad <philippe.moua...@gmail.com> wrote:
<snip/> > Regarding Mirror, in fact I had this "bad ?" :-) idea when debugging Cookie > issue a while ago , I noticed lot of threads were being launched and > Eclipse Debugger went crazy so I had to kill Eclipse. > > In my understanding of Mirror, it is just used during writing phase, so > number of thread is low. Not sure what you mean by "writing phase". I use it for debugging, e.g. seeing what is in a POST request. > If you want to put high numbers then in current implementation, JMeter > performance will go really down since Thread creation has a big cost, so > putting a limit on this is better on this point. Possibly. > Another use of this modification is that you can simulate Server refusing > requests by putting a low value to Threads. Yes, that could be useful. > I don't really understand in which case you will use a mirror in Batch Mode > so an example will help me. See above (POST). > I can rollback it all if you think it's a bad idea. As (I thought) I already wrote, I think it's a bad idea to change the default behaviour. Having an option to limit the threads and limit the queued requests would be useful. So I suggest making the default values 0, and only creating the thread pool and queue if the value is > 0. Again, the documentation needs to be updated to describe how to use the new settings. > Regards > Philipe
