You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Thomas Keller <th...@inatec.com> on 2005/02/04 12:30:02 UTC
JMeter and SSL = slow
Hello!
I'm working with JMeter 2.0.2 (JDK 1.5.0) to create a test case for
our ssl app to test the work load.
SSL is configured on the server with mod_ssl using a self-signed
certificate which works flawlessly in any browser. Since JMeter needs
a PKCS12 certificate to be able to talk to an SSL server I created
this one out of my original certificate/key with
$ openssl pkcs12 -export -in xxxxxx.com.cert -inkey \
devi90.inatec.com.key-insecure -name "xxxxxx.com Test certificate" \
-out xxxxxx.com.p12
and imported it into JMeter via SSL Key Manager.
Now, JMeter makes SSL requests and gets valid responses, but each
request takes between 5 to 10 seconds, while a normal http request
took under a second before. A SSL request in any browser is also
done within a couple of milliseconds.
Am I doing something wrong or have I'm forgotten to configure something?
Thanks for your replies.
--
Best regards | Mit freundlichen Grüßen
Thomas Keller.
inatec solutions GmbH, Public Key 0x94A5F429
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: JMeter and SSL = slow
Posted by Peter Lin <wo...@gmail.com>.
glad it was caused by the cert and you were able to fix it.
unless you stress the server, I doubt you'll see a difference. Many of
the larger E-Commerce sites use bigIP or a SSL enabled router. The
webserver only handles HTTP traffic and the router does all the
encryption. I may have the old numbers Remy and I ran back in 2002. If
I find them, i'll post it.
peter
On Fri, 04 Feb 2005 14:46:48 +0100, Thomas Keller
<th...@inatec.com> wrote:
> Peter Lin schrieb:
> > keep in mind that SSL is heavy weight. By heavy weight I mean this.
> > 450mhz cpu - handles 5-8 concurrent SSL/HTTPS requests, but maxes out cpu
> > 2.0ghz cpu - handles 20-25 concurrent SSL/HTTPS requests, but maxes out cpu
>
> See my previous post... the problem disappeared by now. The long load
> times happened with only one thread running on a 2.4GHz P4 while the
> load on the server machine was not even noticable.
>
> > in general, if you're testing SSL, make sure the sampler isn't set to
> > download the images and other embedded resources.
>
> Yep, I've disabled that anyways.
>
> > I've done quite a
> > bit of testing in the past on the performance difference between HTTPS
> > vs HTTP. You're lucky if the req/sec only drops half. More often than
> > not, depending on how many images you have, it may be 3-5x slower.
> > most large E-commerce sites use hardware accelerators for this reason.
> > IBM, Rainbow technologies and several other companies sell SSL enabled
> > ethernet cards or network attached SSL. Most routers today offer SSL
> > acceleration, so my advice is to not use software SSL. hope that helps
>
> We've been discussed this issue lately, too, and I'm feeling not too
> comfortable using mod_ssl and no hardware accelerated SSL, but as always
> my bosses will not invest in such a thing unless they'll see the current
> system go down under the heavy load.
>
> Thanks for your response.
>
> --
> Best regards | Mit freundlichen Grüßen
> Thomas Keller.
>
> inatec solutions GmbH, Public Key 0x94A5F429
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: JMeter and SSL = slow
Posted by Thomas Keller <th...@inatec.com>.
Peter Lin schrieb:
> keep in mind that SSL is heavy weight. By heavy weight I mean this.
> 450mhz cpu - handles 5-8 concurrent SSL/HTTPS requests, but maxes out cpu
> 2.0ghz cpu - handles 20-25 concurrent SSL/HTTPS requests, but maxes out cpu
See my previous post... the problem disappeared by now. The long load
times happened with only one thread running on a 2.4GHz P4 while the
load on the server machine was not even noticable.
> in general, if you're testing SSL, make sure the sampler isn't set to
> download the images and other embedded resources.
Yep, I've disabled that anyways.
> I've done quite a
> bit of testing in the past on the performance difference between HTTPS
> vs HTTP. You're lucky if the req/sec only drops half. More often than
> not, depending on how many images you have, it may be 3-5x slower.
> most large E-commerce sites use hardware accelerators for this reason.
> IBM, Rainbow technologies and several other companies sell SSL enabled
> ethernet cards or network attached SSL. Most routers today offer SSL
> acceleration, so my advice is to not use software SSL. hope that helps
We've been discussed this issue lately, too, and I'm feeling not too
comfortable using mod_ssl and no hardware accelerated SSL, but as always
my bosses will not invest in such a thing unless they'll see the current
system go down under the heavy load.
Thanks for your response.
--
Best regards | Mit freundlichen Grüßen
Thomas Keller.
inatec solutions GmbH, Public Key 0x94A5F429
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: JMeter and SSL = slow
Posted by Peter Lin <wo...@gmail.com>.
keep in mind that SSL is heavy weight. By heavy weight I mean this.
450mhz cpu - handles 5-8 concurrent SSL/HTTPS requests, but maxes out cpu
2.0ghz cpu - handles 20-25 concurrent SSL/HTTPS requests, but maxes out cpu
in general, if you're testing SSL, make sure the sampler isn't set to
download the images and other embedded resources. I've done quite a
bit of testing in the past on the performance difference between HTTPS
vs HTTP. You're lucky if the req/sec only drops half. More often than
not, depending on how many images you have, it may be 3-5x slower.
most large E-commerce sites use hardware accelerators for this reason.
IBM, Rainbow technologies and several other companies sell SSL enabled
ethernet cards or network attached SSL. Most routers today offer SSL
acceleration, so my advice is to not use software SSL. hope that helps
peter
On Fri, 04 Feb 2005 12:30:02 +0100, Thomas Keller
<th...@inatec.com> wrote:
>
> Hello!
>
> I'm working with JMeter 2.0.2 (JDK 1.5.0) to create a test case for
> our ssl app to test the work load.
> SSL is configured on the server with mod_ssl using a self-signed
> certificate which works flawlessly in any browser. Since JMeter needs
> a PKCS12 certificate to be able to talk to an SSL server I created
> this one out of my original certificate/key with
>
> $ openssl pkcs12 -export -in xxxxxx.com.cert -inkey \
> devi90.inatec.com.key-insecure -name "xxxxxx.com Test certificate" \
> -out xxxxxx.com.p12
>
> and imported it into JMeter via SSL Key Manager.
>
> Now, JMeter makes SSL requests and gets valid responses, but each
> request takes between 5 to 10 seconds, while a normal http request
> took under a second before. A SSL request in any browser is also
> done within a couple of milliseconds.
>
> Am I doing something wrong or have I'm forgotten to configure something?
>
> Thanks for your replies.
>
> --
> Best regards | Mit freundlichen Grüßen
> Thomas Keller.
>
> inatec solutions GmbH, Public Key 0x94A5F429
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org