Re: Bad TPS number reported by the console

No, there's no way to trace what is instrumented. There should be -
please open a Feature Request.

So you are now definitely instrumenting the sendData method and not the
getattr result? (E.g.Test(...).record(impl.sendData))

If so, is sendData() overloaded - are there many variants of the
sendData method?

- Phil

On 11/10/13 17:45, olivier merlin wrote:
> Hello Phil,
>
> I really don't understand, i have used your new instrumentation method
> and i have still the problem
> if i launch one thread with 2 runs, i have:
> Thread, Run, Test, Start time (ms since Epoch), Test time, Errors, SyncML
> 0, 0, 1, 1381509722862, 1, 0, 0.0
> 0, 1, 1, 1381509722867, 0, 0, 0.0
> 0, 1, 1, 1381509722867, 0, 0, 0.0
> 0, 1, 1, 1381509722867, 0, 0, 0.0
> 0, 1, 1, 1381509722867, 0, 0, 0.0
> 0, 1, 1, 1381509722867, 0, 0, 0.0
> 0, 1, 1, 1381509722867, 2, 0, 0.0
> 0, 1, 1, 1381509722871, 0, 0, 0.0
>
> as you can see, the run 1 is executed 7 times.
> Very strange ??
> Do you have an idea on how i can trace the instrumentation ?
>
> cheers,
> Olivier
>
>
> 2013/10/6 Philip Aston <[email protected] <mailto:[email protected]>>
>
>     This is to do with what you are instrumenting, not the logging.
>
>     getattr will return some internal Jython object that represents
>     the bound method. You're instrumenting all methods of this
>     internal Jython object. When you invoke it, the call path is
>     crossing multiple (7!) instrumented methods, but that's completely
>     down to how Jython is implemented.
>
>     Instead I think you should try to instrument the sendData method
>     itself. Try something like:
>
>         Test(...).record(impl.sendData)
>
>         ...
>
>         spResp = impl.sendData(....)
>
>
>     - Phil
>
>
>
>
>
>     On 02/10/13 10:35, olivier merlin wrote:
>>     Hello,
>>
>>     I try to switch our grinder framework to grinder 3.11 and i get a
>>     problem on the TPS count.
>>
>>     When i inject a constant rate of 3 TPS, after a period of X
>>     minutes, the console write a throughput of 21 TPS so x7 the real
>>     throughput.
>>
>>     When looking in the grinder-data_X.log file i see that 3 thread
>>     per second is there but each threads write in the data log 7 times !
>>
>>     I'm quite sure it's a problem of instrumentation somewhere
>>     similar to the bug entered by Phil on the #234  helloworld sample
>>     double counts <http://sourceforge.net/p/grinder/bugs/234/>
>>
>>     *We are using the old way for instrumenting:*
>>     (...)
>>      testSubmit = Test(testId, line.getTestName()).wrap(getattr(impl,
>>     "sendData"))
>>     (...)
>>     spResp = testSubmit(submitCmd,
>>     line.isMemorized(),line.getLastTemplate(), self.memMgr)
>>     (...)
>>
>>     The impl is a protocol implementation that may change between
>>     test - that implements sendData() method.
>>     The problem is perhaps that i switch the logs to logback
>>      (grinder.logger) in all the implementations (like the #234) ...
>>     thus leading to a test record for each logging ?
>>
>>     Do i have to completely change my way of instrumenting ?
>>     Or do i have to use distinct logger from the grinder.logger to
>>     avoid this king of problem ...
>>
>>     Does someone encounter the same trouble ?
>>
>>     cheers,
>>     Olivier  
>

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk

_______________________________________________
grinder-use mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/grinder-use