You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by Vladimir Sitnikov <si...@gmail.com> on 2023/12/01 11:01:57 UTC
Require Java 17 in JMeter 6
Hi,
Previously, we discussed bumping Java requirements to 11, and there were no
complaints.
Now I suggest we consider requiring Java 17 instead.
I think it should not be a problem as Java 17 was released quite a while
ago, and the users should be able to upgrade the runtime.
Many users execute JMeter with Java 17+ already (e.g. due to security and
performance reasons),
and upgrading Java would probably fix many Swing problems.
Any thoughts on this?
Vladimir
Re: Require Java 17 in JMeter 6
Posted by Philippe Mouawad <p....@ubik-ingenierie.com>.
Hello,
Ok by me, good idea
Regarde
Le ven. 1 déc. 2023 à 13:10, Felix Schumacher <
felix.schumacher@internetallee.de> a écrit :
>
>
> Am 1. Dezember 2023 12:01:57 MEZ schrieb Vladimir Sitnikov <
> sitnikov.vladimir@gmail.com>:
> >Hi,
> >
> >Previously, we discussed bumping Java requirements to 11, and there were
> no
> >complaints.
> >
> >Now I suggest we consider requiring Java 17 instead.
> >I think it should not be a problem as Java 17 was released quite a while
> >ago, and the users should be able to upgrade the runtime.
> >
> >Many users execute JMeter with Java 17+ already (e.g. due to security and
> >performance reasons),
> >and upgrading Java would probably fix many Swing problems.
> >
> >Any thoughts on this?
>
> I think it is great to move forward.
>
> Felix
>
> >
> >Vladimir
>
Re: Require Java 17 in JMeter 6
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 1. Dezember 2023 12:01:57 MEZ schrieb Vladimir Sitnikov <si...@gmail.com>:
>Hi,
>
>Previously, we discussed bumping Java requirements to 11, and there were no
>complaints.
>
>Now I suggest we consider requiring Java 17 instead.
>I think it should not be a problem as Java 17 was released quite a while
>ago, and the users should be able to upgrade the runtime.
>
>Many users execute JMeter with Java 17+ already (e.g. due to security and
>performance reasons),
>and upgrading Java would probably fix many Swing problems.
>
>Any thoughts on this?
I think it is great to move forward.
Felix
>
>Vladimir
Re: Require Java 17 in JMeter 6
Posted by Antonio Gomes Rodrigues <ra...@gmail.com>.
Hi,
Ok too with use Java17 instead of Java11
Le ven. 1 déc. 2023 à 12:03, Vladimir Sitnikov <si...@gmail.com>
a écrit :
> Hi,
>
> Previously, we discussed bumping Java requirements to 11, and there were no
> complaints.
>
> Now I suggest we consider requiring Java 17 instead.
> I think it should not be a problem as Java 17 was released quite a while
> ago, and the users should be able to upgrade the runtime.
>
> Many users execute JMeter with Java 17+ already (e.g. due to security and
> performance reasons),
> and upgrading Java would probably fix many Swing problems.
>
> Any thoughts on this?
>
> Vladimir
>
Re: Require Java 17 in JMeter 6
Posted by Milamber <mi...@apache.org>.
Ok so, seems that next JMeter major version (v6) will have as
requirement at least Java 17 LTS+
On 04/12/2023 10:24, Vladimir Sitnikov wrote:
> Java 21 was released just a couple of months ago, so it might be too early
> to require Java 21 for the execution. We should probably support at least
> two LTS releases.
>
> Vladimir
>
Re: Require Java 17 in JMeter 6
Posted by Vladimir Sitnikov <si...@gmail.com>.
Java 21 was released just a couple of months ago, so it might be too early
to require Java 21 for the execution. We should probably support at least
two LTS releases.
Vladimir
Re: Require Java 17 in JMeter 6
Posted by Milamber <mi...@apache.org>.
Hi,
Thanks Jerry for comments.
@PMC would you open a vote thread for JMeter 6 support JVM ? with Java
17 or Java 21 ?
Milamber
On 01/12/2023 19:11, Jerry Andrews wrote:
> I am a member of the Java success team at Oracle, and a senior application architect. I've been a JMeter user and advocate for a long time.
>
> As a programmer, the benefits of going to Java 17 are obvious, I hope. Code is easier to write, easier to read, and more efficient. The Java 8 Enterprise Performance Pack provides Java 17 performance to Java 8 users, but is only available to Java subscribers, who support the continued maintenance of Java 8 and other past-end-of-public-releases versions.
> The long term support versions of Java are 8, 11, 17, and now 21. Java 11 public support ended in September 2023. Public support for Java 17 ends in September of 2026.
> I would strongly recommend that JMeter move to Java 17 or Java 21 immediately. Furthermore, the new lightweight threads available in Java 21 would be a huge performance boost to JMeter, so I strongly recommend that JMeter move to Java 21 as soon as practical after moving to Java 11. Running JMeter in a different VM from the application under test should be no burden to users, and the reduced cost in building a test environment due to improved thread efficiency should well offset the increased effort in adding a VM specifically for running JMeter.
> I further suggest that, if bandwidth allows, that the team consider testing JMeter on GraalVM, which has significant performance benefits over other VMs. Getting JMeter to run in compiled form might also offer certain benefits in terms of startup performance and repeatability (but we'd have to test that).
> Jerry Andrews
> Master Principal Java Success Consultant
> Oracle Corporation
>
> On Dec 1 2023, at 8:39 am, Milamber <mi...@apache.org> wrote:
>> Hi,
>>
>> I agree to move from Java 8 to Java 17 directly because :
>> 1/ that is an opportunity to have better code on better runtime (jvm) for JMeter
>> 2/ Moving from 8 to 17 will add improvements from 8 to 17 include v11.
>> 3/ I hope that the JMeter's ecosystem (jmeter-plugins, etc.) can move to 17, for best plugins/add-on.
>> 4/ I hope to have more contributor sfor JMeter core if using lasted LTS version of Java.
>> @Vincent, I have display issues with VRT and Java 17 (17.0.9 from Oracle), see screenshot.
>> Milamber
>>
>>
>> On 01/12/2023 13:39, Vincent Daburon wrote:
>>> Hi,
>>> The jdk11 had some issues when display text in view tree listener, it could be very long to display a short text.
>>>
>>> I am totally ok for jdk 17 LTS in new JMeter 6
>>>
>>> Regards
>>> Vincent Dab
>>>
>>>
>>>> Le 1 déc. 2023 à 12:03, Vladimir Sitnikov <si...@gmail.com> (mailto:sitnikov.vladimir@gmail.com) a écrit :
>>>>
>>>> Hi,
>>>>
>>>> Previously, we discussed bumping Java requirements to 11, and there were no
>>>> complaints.
>>>>
>>>> Now I suggest we consider requiring Java 17 instead.
>>>> I think it should not be a problem as Java 17 was released quite a while
>>>> ago, and the users should be able to upgrade the runtime.
>>>>
>>>> Many users execute JMeter with Java 17+ already (e.g. due to security and
>>>> performance reasons),
>>>> and upgrading Java would probably fix many Swing problems.
>>>>
>>>> Any thoughts on this?
>>>>
>>>> Vladimir
>
Re: Require Java 17 in JMeter 6
Posted by Jerry Andrews <je...@jrandrews.org>.
I am a member of the Java success team at Oracle, and a senior application architect. I've been a JMeter user and advocate for a long time.
As a programmer, the benefits of going to Java 17 are obvious, I hope. Code is easier to write, easier to read, and more efficient. The Java 8 Enterprise Performance Pack provides Java 17 performance to Java 8 users, but is only available to Java subscribers, who support the continued maintenance of Java 8 and other past-end-of-public-releases versions.
The long term support versions of Java are 8, 11, 17, and now 21. Java 11 public support ended in September 2023. Public support for Java 17 ends in September of 2026.
I would strongly recommend that JMeter move to Java 17 or Java 21 immediately. Furthermore, the new lightweight threads available in Java 21 would be a huge performance boost to JMeter, so I strongly recommend that JMeter move to Java 21 as soon as practical after moving to Java 11. Running JMeter in a different VM from the application under test should be no burden to users, and the reduced cost in building a test environment due to improved thread efficiency should well offset the increased effort in adding a VM specifically for running JMeter.
I further suggest that, if bandwidth allows, that the team consider testing JMeter on GraalVM, which has significant performance benefits over other VMs. Getting JMeter to run in compiled form might also offer certain benefits in terms of startup performance and repeatability (but we'd have to test that).
Jerry Andrews
Master Principal Java Success Consultant
Oracle Corporation
On Dec 1 2023, at 8:39 am, Milamber <mi...@apache.org> wrote:
> Hi,
>
> I agree to move from Java 8 to Java 17 directly because :
> 1/ that is an opportunity to have better code on better runtime (jvm) for JMeter
> 2/ Moving from 8 to 17 will add improvements from 8 to 17 include v11.
> 3/ I hope that the JMeter's ecosystem (jmeter-plugins, etc.) can move to 17, for best plugins/add-on.
> 4/ I hope to have more contributor sfor JMeter core if using lasted LTS version of Java.
> @Vincent, I have display issues with VRT and Java 17 (17.0.9 from Oracle), see screenshot.
> Milamber
>
>
> On 01/12/2023 13:39, Vincent Daburon wrote:
> >
> > Hi,
> > The jdk11 had some issues when display text in view tree listener, it could be very long to display a short text.
> >
> > I am totally ok for jdk 17 LTS in new JMeter 6
> >
> > Regards
> > Vincent Dab
> >
> >
> > > Le 1 déc. 2023 à 12:03, Vladimir Sitnikov <si...@gmail.com> (mailto:sitnikov.vladimir@gmail.com) a écrit :
> > >
> > > Hi,
> > >
> > > Previously, we discussed bumping Java requirements to 11, and there were no
> > > complaints.
> > >
> > > Now I suggest we consider requiring Java 17 instead.
> > > I think it should not be a problem as Java 17 was released quite a while
> > > ago, and the users should be able to upgrade the runtime.
> > >
> > > Many users execute JMeter with Java 17+ already (e.g. due to security and
> > > performance reasons),
> > > and upgrading Java would probably fix many Swing problems.
> > >
> > > Any thoughts on this?
> > >
> > > Vladimir
> >
>
Re: Require Java 17 in JMeter 6
Posted by Milamber <mi...@apache.org>.
Hi,
I agree to move from Java 8 to Java 17 directly because :
1/ that is an opportunity to have better code on better runtime (jvm)
for JMeter
2/ Moving from 8 to 17 will add improvements from 8 to 17 include v11.
3/ I hope that the JMeter's ecosystem (jmeter-plugins, etc.) can move to
17, for best plugins/add-on.
4/ I hope to have more contributor sfor JMeter core if using lasted LTS
version of Java.
@Vincent, I have display issues with VRT and Java 17 (17.0.9 from
Oracle), see screenshot.
Milamber
On 01/12/2023 13:39, Vincent Daburon wrote:
> Hi,
> The jdk11 had some issues when display text in view tree listener, it could be very long to display a short text.
>
> I am totally ok for jdk 17 LTS in new JMeter 6
>
> Regards
> Vincent Dab
>
>
>> Le 1 déc. 2023 à 12:03, Vladimir Sitnikov <si...@gmail.com> a écrit :
>>
>> Hi,
>>
>> Previously, we discussed bumping Java requirements to 11, and there were no
>> complaints.
>>
>> Now I suggest we consider requiring Java 17 instead.
>> I think it should not be a problem as Java 17 was released quite a while
>> ago, and the users should be able to upgrade the runtime.
>>
>> Many users execute JMeter with Java 17+ already (e.g. due to security and
>> performance reasons),
>> and upgrading Java would probably fix many Swing problems.
>>
>> Any thoughts on this?
>>
>> Vladimir
Re: Require Java 17 in JMeter 6
Posted by Vincent Daburon <vd...@gmail.com>.
Hi,
The jdk11 had some issues when display text in view tree listener, it could be very long to display a short text.
I am totally ok for jdk 17 LTS in new JMeter 6
Regards
Vincent Dab
> Le 1 déc. 2023 à 12:03, Vladimir Sitnikov <si...@gmail.com> a écrit :
>
> Hi,
>
> Previously, we discussed bumping Java requirements to 11, and there were no
> complaints.
>
> Now I suggest we consider requiring Java 17 instead.
> I think it should not be a problem as Java 17 was released quite a while
> ago, and the users should be able to upgrade the runtime.
>
> Many users execute JMeter with Java 17+ already (e.g. due to security and
> performance reasons),
> and upgrading Java would probably fix many Swing problems.
>
> Any thoughts on this?
>
> Vladimir