Performance Plugin

29 views
Skip to first unread message

Ostermueller, Erik

unread,
Jan 26, 2015, 5:09:11 PM1/26/15
to jenkins...@googlegroups.com, man...@apache.org

Hello,

 

I have two questions about the performance plugin.  I’ve got 1.11, Jenkins 1.590 on linux, openjdk 1.7x.

 

First, how do you delete/expire the cache that was added in V1.10 ?

 

Second, my most recent build’s .jtl file is a concatenation of the current build and multiple .jtl files from prior builds.  Is this intentional?  The concatenation doesn’t seem to happen consistently.  Without it, my throughput graphs look great.  But when my .jtl has data concatenated from multiple builds, the throughput numbers are like 0 or 1 and completely disagree with the verbose JMeter output (that looks correct to me), which is seen in the build log.

 

Thanks for Jenkins.

 

--Erik

 

_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.

Erik Ostermueller

unread,
Feb 16, 2015, 4:09:05 PM2/16/15
to jenkins...@googlegroups.com, man...@apache.org, erik.ost...@fisglobal.com
Replying to self here.
Weeks ago, I wrote:
>> my .jtl has data concatenated from multiple builds,

That was my problem and I fixed it by using the Jenkins options to delete my Jenkins "workspace" before each build.  Otherwise, JMeter's default behavior is to append new data to an existing .jtl file, no matter how old that .jtl file is.

Say that I had run builds from the 10 previous evenings, each with a 2-minute load test.
I was left with a single .jtl file that had a two minute load test followed by 23 hours and 58 minutes of inactivity...and then repeat that 9 more times.
All that inactivity graphed as near-zero throughput.

--Erik
Reply all
Reply to author
Forward
0 new messages