[prev in list] [next in list] [prev in thread] [next in thread]
List: grinder-use
Subject: Re: [Grinder-use] Reported timing
From: Marc Holden <mholden123 () gmail ! com>
Date: 2015-12-18 16:20:33
Message-ID: CADV_OVVhoAXEeERhdeQLJDNLnr68H_=aVcdZL+GtH7zGP5de8g () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi Sean,
Have you tried to ignoring the few sample sets that come in and allow the
test to run for a few minutes. There may be class
loading/caching/instrumentation/networking latency you are experiencing.
-Marc
On Fri, Dec 18, 2015 at 10:37 AM Sean Tiley <sean.tiley@gmail.com> wrote:
> Hi Gary,
> I ran the test once and captured the following stats from the console
>
> 200 Page 2 - Login 631
> 201 GET start.swe - 338
> 202 GET login.css - 18
> 203 GET swen_tp.js - 18
> 204 GET log7_d.gif - 19
> 205 GET login.js - 7
> 206 GET swecmhi.js - 20
> 207 GET swi_top.js - 23
> 208 GET swecoon.js - 17
> 209 GET do-not.png - 10
> 210 GET logint.jpg - 29
> 211 GET loginr.jpg - 13
> 212 GET transt.gif - 18
> 213 GET favcon.ico - 9
>
> Adding times for 201-213 gives 539. That leaves a difference of 92.
>
>
> my page 2 function looks like this, (unnecessary bits removed). There are
> 2 explicit sleeps in the page 2 code for a total of 62, leaving 30
> unaccounted for.
>
>
> def page2(self):
> """GET start.swe (requests 201-213)."""
> result = request201.GET(...)
> request202.GET(...)
> request203.GET(...)
> request204.GET(...)
> request205.GET(...)
> request206.GET(...)
> request207.GET(....)
> request208.GET(...)
>
> grinder.sleep(15)
>
> request209.GET(...)
> request210.GET(...)
> request211.GET(...)
> request212.GET(...)
>
> grinder.sleep(47)
>
> request213.GET(...)
> return result
>
>
> In the __call__
> I have the following
>
> def __call__(self):
> grinder.getStatistics().setDelayReports(True)
> """Called for every run performed by the worker thread."""
> self.page1() # GET / (request 101)
>
> grinder.sleep(47)
> self.page2() # GET start.swe (requests 201-213)
>
> grinder.sleep(10188)
> self.page3() # POST start.swe (request 301)
>
> ......snip
>
>
> There is an explicit sleep of 47 between page 1 and 2 but I think the
> times here are varied slightly automatically from thread to thread and not
> counted in the reported times?
>
> So not really sure where the addidional time comes from?
>
> Any thoughts are welcomed
>
> Thanks
>
>
> Sean
>
> ------------------------------------------------------------------------------
> _______________________________________________
> grinder-use mailing list
> grinder-use@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/grinder-use
>
[Attachment #5 (text/html)]
<div dir="ltr">Hi Sean,<div><br></div><div>Have you tried to ignoring the few sample \
sets that come in and allow the test to run for a few minutes. There may be class \
loading/caching/instrumentation/networking latency you are experiencing. \
</div><div><br></div><div>-Marc </div></div><br><div class="gmail_quote"><div \
dir="ltr">On Fri, Dec 18, 2015 at 10:37 AM Sean Tiley <<a \
href="mailto:sean.tiley@gmail.com">sean.tiley@gmail.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><p>Hi Gary,<br>I ran \
the test once and captured the following stats from the console</p><p>200 Page 2 - \
Login 631<br>201 GET start.swe - 338<br>202 GET login.css - 18<br>203 GET \
swen_tp.js - 18<br>204 GET log7_d.gif - 19<br>205 GET login.js - 7<br>206 GET \
swecmhi.js - 20<br>207 GET swi_top.js - 23<br>208 GET swecoon.js - 17<br>209 GET \
do-not.png - 10<br>210 GET logint.jpg - 29<br>211 GET loginr.jpg - 13<br>212 GET \
transt.gif - 18<br>213 GET favcon.ico - 9</p><p>Adding times for 201-213 gives 539. \
That leaves a difference of 92.</p><p><br></p><p>my page 2 function looks like this, \
(unnecessary bits removed). There are 2 explicit sleeps in the page 2 code for a \
total of 62, leaving 30 unaccounted for.</p><p><br> def page2(self):<br> \
"""GET start.swe (requests 201-213)."""<br> \
result = request201.GET(...)<br> request202.GET(...)<br> \
request203.GET(...)<br> request204.GET(...)<br> request205.GET(...)<br> \
request206.GET(...)<br> request207.GET(....)<br> \
request208.GET(...)</p><p> grinder.sleep(15)</p><p> \
request209.GET(...)<br> request210.GET(...)<br> request211.GET(...)<br> \
request212.GET(...)</p><p> grinder.sleep(47)</p><p> \
request213.GET(...)<br> return result</p><p> <br>In the __call__<br>I have the \
following</p><p> def __call__(self):<br> \
grinder.getStatistics().setDelayReports(True)<br> """Called for \
every run performed by the worker thread."""<br> self.page1() \
# GET / (request 101)</p><p> grinder.sleep(47)<br> self.page2() \
# GET start.swe (requests 201-213)</p><p> grinder.sleep(10188)<br> \
self.page3() # POST start.swe (request \
301)</p><p>......snip</p><p><br>There is an explicit sleep of 47 between page 1 and 2 \
but I think the times here are varied slightly automatically from thread to thread \
and not counted in the reported times? </p><p>So not really sure where the \
addidional time comes from?</p><p>Any thoughts are \
welcomed</p><p>Thanks</p></div><div dir="ltr"><p><br>Sean</p></div>
------------------------------------------------------------------------------<br>
_______________________________________________<br>
grinder-use mailing list<br>
<a href="mailto:grinder-use@lists.sourceforge.net" \
target="_blank">grinder-use@lists.sourceforge.net</a><br> <a \
href="https://lists.sourceforge.net/lists/listinfo/grinder-use" rel="noreferrer" \
target="_blank">https://lists.sourceforge.net/lists/listinfo/grinder-use</a><br> \
</blockquote></div>
------------------------------------------------------------------------------
_______________________________________________
grinder-use mailing list
grinder-use@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/grinder-use
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic