https://issues.apache.org/bugzilla/show_bug.cgi?id=53748
--- Comment #10 from ejaenv <[email protected]> --- Yes this is a beta version and surely the design needs to be discussed. As it is now: >If the access log does need to be reformatted, it should be done as a separate >>stage before starting the test proper, and the output should probably be >>reformatted to make subsequent parsing easier. Yes, this is done in a separate stage. >I'm not sure why the access log needs to be rewritten, surely the sampler can >>just read through the file until it finds the correct entry? Each sampler > would need to know the IP address for which it is responsible. As in the current plugin design, a log preprocessing is done: 1. to know in advance how many threadgroups will have the test plan (one for IP) 2. to know how many requests each IP will send, and close the threadgroup when it has finished. Rewritting the acceslog is done for efficiency, to avoid each sampler read the whole log file, but apart of this, yes, it's possible for a sampler to work directly with the original file. >I don't think this should be added to JMeter trunk without further analysis. >Maybe create an SVN branch so the feature can be tested further. >If it looks OK it can later be merged with trunk. I agree! Probably its better a design without preprocessing, where a master sampler reads the log, and dynamically creates slave threadgroups on demand. This would also solve the file hander problem you pointed earlier. -- You are receiving this mail because: You are the assignee for the bug.
