Re: Let's release a Major 3.3 version !

[Philippe Mouawad]

+1

We need to update new and noteworthy section though.

Regards
On Friday, September 15, 2017, Antonio Gomes Rodrigues 
wrote:

> +1
>
> Antonio
>
> 2017-09-15 23:23 GMT+02:00 Milamber  >:
>
> > Hello,
> >
> > Ready for me to prepare version 3.3 RC1 of JMeter?
> >
> > Milamber
> >
> >
> > On 05/09/2017 18:44, Milamber wrote:
> >
> >>
> >>
> >> On 05/09/2017 12:42, Philippe Mouawad wrote:
> >>
> >>> Hello,
> >>> This has been running since june :-)
> >>> Now version has become a major one with 33 bug fixes and 13
> enhancements.
> >>>
> >>> It would be nice if we could prepare a release by end of this week if
> >>> release manager is ready to
> >>>
> >>
> >> Unfortunately I will travel to Amsterdam from Thursday to Sunday. I
> could
> >> start the RC1 next weekend (16th september) if you are ok.
> >>
> >>
> >>
> >>
> >>
> >
>


-- 
Cordialement.
Philippe Mouawad.

Re: Let's release a Major 3.3 version !

[Antonio Gomes Rodrigues]

+1

Antonio

2017-09-15 23:23 GMT+02:00 Milamber :

> Hello,
>
> Ready for me to prepare version 3.3 RC1 of JMeter?
>
> Milamber
>
>
> On 05/09/2017 18:44, Milamber wrote:
>
>>
>>
>> On 05/09/2017 12:42, Philippe Mouawad wrote:
>>
>>> Hello,
>>> This has been running since june :-)
>>> Now version has become a major one with 33 bug fixes and 13 enhancements.
>>>
>>> It would be nice if we could prepare a release by end of this week if
>>> release manager is ready to
>>>
>>
>> Unfortunately I will travel to Amsterdam from Thursday to Sunday. I could
>> start the RC1 next weekend (16th september) if you are ok.
>>
>>
>>
>>
>>
>

Re: Let's release a Major 3.3 version !

[Milamber]

Hello,

Ready for me to prepare version 3.3 RC1 of JMeter?

Milamber

On 05/09/2017 18:44, Milamber wrote:



On 05/09/2017 12:42, Philippe Mouawad wrote:

Hello,
This has been running since june :-)
Now version has become a major one with 33 bug fixes and 13 
enhancements.


It would be nice if we could prepare a release by end of this week if
release manager is ready to


Unfortunately I will travel to Amsterdam from Thursday to Sunday. I 
could start the RC1 next weekend (16th september) if you are ok.

vs requests graph configs

[Jenna Krappa]

 Hi All,

I am generating some custom graphs and would like to know how I can set the
Vs Requests graphs to include lines between the plotted points. I haven't
been able to find a setting in the properties file or which section of the
code needs to be changed.

Thanks in advance,
Jenna Krappa

Re: GUI guideline

[Antonio Gomes Rodrigues]

Hi Vladimir,

Thank to you answer

We are 2 who prefer accesslogsampler.png for the moment :-)

Maybe if other are ok and nobody plan to migrate GUI to other technology
(JavaFX, Web...) it's time to have a more homogeneous GUI for JMeter

Antonio



2017-09-15 20:59 GMT+02:00 Vladimir Sitnikov :

> Hi,
>
> I don't know if a guideline exists, however I do like accesslogsampler.png
> better (left edges of text fields aligned while the labels are
> right-aligned)
>
> The same UI is produced by JMeter's BeanInfoSupport-based generated UIs.
>
> Vladimir
>

[GitHub] jmeter pull request #307: Bug61525 : OS Process Sampler : Add browser button...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/jmeter/pull/307


---

Re: GUI guideline

[Vladimir Sitnikov]

Hi,

I don't know if a guideline exists, however I do like accesslogsampler.png
better (left edges of text fields aligned while the labels are
right-aligned)

The same UI is produced by JMeter's BeanInfoSupport-based generated UIs.

Vladimir

[GitHub] jmeter pull request #307: Bug61525 : OS Process Sampler : Add browser button...

[ra0077]

GitHub user ra0077 opened a pull request:

https://github.com/apache/jmeter/pull/307

Bug61525 : OS Process Sampler : Add browser button to Command and Wor…

…king directory fields

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ra0077/jmeter trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/jmeter/pull/307.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #307


commit af3142ca0efc0ec85fa90bb4e722d9f0438e1fcc
Author: ra77 
Date:   2017-09-15T18:53:55Z

Bug61525 : OS Process Sampler : Add browser button to Command and Working 
directory fields




---

GUI guideline

[Antonio Gomes Rodrigues]

Hi all,

I have a question about JMeter GUI

In some element, TextField are aligned to the left
For example,  Default Test Values field in Access Log Sampler
http://jmeter.apache.org/images/screenshots/accesslogsampler.png

And in other, it's the label which are aligned to the left
For example, Counter sampler
http://jmeter.apache.org/images/screenshots/counter.png

I have a preference for the first solution

Is there a choice?

Antonio

Re: Netty Client Implementation for HTTP Sampler

[Isuru Perera]

Hi Philippe,

Thanks a lot for your comments.

I tested on EC2. I followed best practices in
http://jmeter.apache.org/usermanual/best-practices.html. For example, I
used non-GUI mode and I only have one HTTP sampler in the test.

I still couldn't find time to see why JMeter load average high. Next time,
I will try to profile JMeter and see where the CPU was consumed etc.

I actually mentioned about JMeter Architecture as each user is a thread in
JMeter. I think more threads might have an impact to the load average, but
I cannot confirm without having data to prove it. I'm also hoping to try
out off-cpu flamegraphs as explained in
http://www.brendangregg.com/blog/2017-08-08/linux-load-averages.html

I will reply once I have flamegraphs, CPU profiling data, etc. Please note
that it will take some more time :)

Thanks for your help.

Best Regards,


On Tue, Sep 12, 2017 at 7:13 PM, Philippe Mouawad <
p.moua...@ubik-ingenierie.com> wrote:

> Hi,
> Find my answers below.
> Regards
>
> On Tue, Sep 12, 2017 at 4:49 AM, Isuru Perera  wrote:
>
>> Hi Philippe,
>>
>> Thanks a lot for your comments
>>
>> I have actually tested concurrent users up to 2000 in non-GUI mode and I
>> didn't have any issues. As I mentioned earlier, the load average of the
>> JMeter server is very high. Therefore I wanted to find out why the load
>> average is very high. One reason could be that there is one thread per
>> user. So, 2000 users mean 2000 threads, which can be very high for a server
>> to handle. Could you also please check the load average of the server when
>> you are running a test with more than 1000 concurrent users? I hope you
>> will also observe high load average.
>>
> No it is not high, if it was I would be worried :-) about the accurateness
> of my results.
>
> What is the configuration of your server  ?
> Are you following best-practices in tests ,  scripting, configuration ?
> Did you make some thread dumps or profile to see where CPU was consumed
> for example ?
> Could you share your plan ? privately ?
>
>
>>
>> Most people I work with are really concerned about the load average. Since
>> one thread per user is a core part of JMeter architecture, I thought may be
>> using an asynchronous HTTP client like Netty will help to reduce the load
>> average of the server. That's why I started this mail thread.
>>
>
> I understand and as I wrote your thinking is good for me, but the
> correlation you make between High Load and JMeter architecture might not be
> correct.
>
> If I had to create a whole new JMeter today , I would go for a different
> architecture, still I use JMeter for pretty high loads without issues and
> keep in mind that once you've set aside CPU consumption, a machine has
> other limitations particularly on network side.
>
>
>> I would love to contribute to JMeter, but I need to first invest some
>> time to understand existing code base.
>>
> Absolutely. If you need help, feel free to ask questions.
> And as usual, start with small issues, medium then big pieces to get
> comfortable with code.
>
>
>>
>> On Mon, Sep 11, 2017 at 5:08 PM, Philippe Mouawad <
>> philippe.moua...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>>
>>> On Mon, Sep 11, 2017 at 8:26 AM, Isuru Perera 
>>> wrote:
>>>
 Hi Philippe,

 I'm sorry for not explaining my reasons sooner.

 So, the main reason for asking about a Netty Client Implementation for
 HTTP Sampler is that Netty is supposed to be better at working under large
 number of  concurrent non blocking connections.

 The main issues we are having with current HTTP Sampler are:

1. Load Average of the JMeter instance is very high. See thread:
http://www.jmeter-archive.org/Maximum-number-of-concurrent-u
sers-td5726006.html

 .
Even for low number of concurrent users (eg, 300), if there is no timers
added to the test plan, the load average of the client goes beyond
acceptable limits.

 Not being able to go above 300 threads is  due to wrong configuration,
>>> bad scripting practices, GUI usage ...
>>> For example, In our experience, on a 8vCPU, 16 Gb RAM, you can easily go
>>> up to 2000 / 3000 threads depending on test. Have a look on recent
>>> benchmarks done on last JMeter versions.
>>> So I think this particular case is not relevant.
>>>


1. With the default value for "httpclient4.time_to_live", we see
very high response times. When we increase the time_to_live value for 30
minutes to keep a fixed number of connections, the response times are 
 much
better. See also http://www.jmeter-archive.org/
Number-of-open-connections-vary-with-time-tp5726000p5726123.html

 


>>> The default value for "httpclient4.time_to_live" is by definit