https://issues.apache.org/bugzilla/show_bug.cgi?id=53748
--- Comment #7 from Philippe Mouawad <[email protected]> --- (In reply to ejaenv from comment #6) > Hi Philippe, > > Sorry me too! > > Thanks for your questions. I hope to clarify them: > > - Why read lines from access log into memory instead of reading them from > file ? > > This is needed to keep at runtime the delays as similar as in the log file. > Reading them from disc caused delay deviations due to disc major latency. > In this case , I think it's better to parse time during read and only store the time instead of the whole sampler ? Also I wonder if it would not be better to read from file to decrease memory usage. > - There is something that's not clear for me, does Access Log TImeer suppose > that access log file has been split into as many file as IPs and that only > the logs concerning the Thread Group under which Timer is located are passed > to it ? because if not, it seems to me delay computation is weird ? could > you clarify ? > > yes, the generator (1) splits the log file in the way you say, and also > generates the jmeter plan file. Keep in mind that this computation is done > before running jmeter, in a preparation phase. > > (1) the generator is implemented actually as a junit test, but the idea is > to have a command tool. > > - Could you submit the PDF into a writable format ? > > I attach it. > > > Best regards, > /Enric Could you join the dev mailing list, I started a discussion "AccessLogSampler & Bug 53748" ? -- You are receiving this mail because: You are the assignee for the bug.
