Re: [openssl-users] OpenSSL s_time output meaning

[danigrosu]

> I'm not sure what use that information might be to you, since you haven't
told us why you're running s_time in the first place.

So that is why I am running s_time, to benchmark my customised Apache
server.
I had a little difficulty with its output. :D

Best wishes,
Dani Grosu

On 1 July 2016 at 16:12, Salz, Rich [via OpenSSL] <
ml-node+s6102n67168...@n7.nabble.com> wrote:

> Not answering the question, but that is a pretty cool thing you built!
> --
> openssl-users mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://openssl.6102.n7.nabble.com/OpenSSL-s-time-output-meaning-tp67092p67168.html
> To unsubscribe from OpenSSL s_time output meaning, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://openssl.6102.n7.nabble.com/OpenSSL-s-time-output-meaning-tp67092p67170.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] OpenSSL s_time output meaning

[Salz, Rich]

Not answering the question, but that is a pretty cool thing you built!
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] OpenSSL s_time output meaning

[Daniel Grosu]

I've created an OpenSSL engine in order to use the GPU for RSA operations
(modular exponentiation) and I have integrated this engine with mod_ssl in
the Apache web server.
So, knowing about s_time command, I wanted to obtain the number of secured
connections per sec that Apache can handle using my engine.

Thank you for the support.

Best wishes,
Dani Grosu
On 30 Jun 2016 22:00, "Michael Wojcik" <michael.woj...@microfocus.com>
wrote:

> > From: openssl-users [mailto:[hidden email]
> <http:///user/SendEmail.jtp?type=node=67153=0>] On Behalf
> > Of danigrosu
> > Sent: Tuesday, June 28, 2016 22:57
> > To: [hidden email] <http:///user/SendEmail.jtp?type=node=67153=1>
> > Subject: [openssl-users] OpenSSL s_time output meaning
> >
> > Using the `$ openssl s_time -connect localhost:443 -new -time 30`
> command
> > gives this output:
> >
> > No CIPHER specified
> > Collecting connection statistics for 30 seconds
> > ** etc.
> > 8102 connections in 12.65s; 640.47 connections/user sec, bytes read 0
> > 8102 connections in 31 real seconds, 0 bytes read per connection
> >
> > What is the difference between 8102 connections in 12.65s and 8102
> > connections in 31 real seconds ?
>
> Use the source, Luke.
>
> Yes, the output is confusing; "real seconds" is not a particularly
> meaningful term. (What, the imaginary part is zero?) The value that's
> displayed there is the "wall-clock time" elapsed between the start of the
> test and when the report is produced. It's the sum of the time specified by
> -time (or the 30s default) plus the overhead that's not counted while
> timing actual OpenSSL operations, rounded to 1-second granularity.
>
> The 12.65s in the first line is the value of "totalTime", which is the
> accumulator for the timer the openssl command uses for timing the test. The
> s_time command starts this timer before the connection loop and stops it
> after the loop. The timer (in this case) counts only "user" time, that is
> time the process spends in user mode; that's why that line says "user sec".
>
> So this is telling you that your system uses about 1.5ms of user-mode CPU
> time per connection, and that it was able to make about 270 connections per
> second.
>
> I'm not sure what use that information might be to you, since you haven't
> told us why you're running s_time in the first place.
>
> --
> Michael Wojcik
> Technology Specialist, Micro Focus
> --
> openssl-users mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://openssl.6102.n7.nabble.com/OpenSSL-s-time-output-meaning-tp67092p67153.html
> To unsubscribe from OpenSSL s_time output meaning, click here
> <http://openssl.6102.n7.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code=67092=ZG5pLmdyb3N1QGdtYWlsLmNvbXw2NzA5MnwtMTk3MTUwMDcxNg==>
> .
> NAML
> <http://openssl.6102.n7.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] OpenSSL s_time output meaning

[Michael Wojcik]

> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of danigrosu
> Sent: Tuesday, June 28, 2016 22:57
> To: openssl-users@openssl.org
> Subject: [openssl-users] OpenSSL s_time output meaning
> 
> Using the `$ openssl s_time -connect localhost:443 -new -time 30` command
> gives this output:
> 
> No CIPHER specified
> Collecting connection statistics for 30 seconds
> ** etc.
> 8102 connections in 12.65s; 640.47 connections/user sec, bytes read 0
> 8102 connections in 31 real seconds, 0 bytes read per connection
> 
> What is the difference between 8102 connections in 12.65s and 8102
> connections in 31 real seconds ?

Use the source, Luke.

Yes, the output is confusing; "real seconds" is not a particularly meaningful 
term. (What, the imaginary part is zero?) The value that's displayed there is 
the "wall-clock time" elapsed between the start of the test and when the report 
is produced. It's the sum of the time specified by -time (or the 30s default) 
plus the overhead that's not counted while timing actual OpenSSL operations, 
rounded to 1-second granularity.

The 12.65s in the first line is the value of "totalTime", which is the 
accumulator for the timer the openssl command uses for timing the test. The 
s_time command starts this timer before the connection loop and stops it after 
the loop. The timer (in this case) counts only "user" time, that is time the 
process spends in user mode; that's why that line says "user sec".

So this is telling you that your system uses about 1.5ms of user-mode CPU time 
per connection, and that it was able to make about 270 connections per second.

I'm not sure what use that information might be to you, since you haven't told 
us why you're running s_time in the first place.

-- 
Michael Wojcik
Technology Specialist, Micro Focus
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

[openssl-users] OpenSSL s_time output meaning

[danigrosu]

Using the `$ openssl s_time -connect localhost:443 -new -time 30` command
gives this output:

No CIPHER specified
Collecting connection statistics for 30 seconds
** etc.
8102 connections in 12.65s; 640.47 connections/user sec, bytes read 0
8102 connections in 31 real seconds, 0 bytes read per connection

What is the difference between 8102 connections in 12.65s and 8102
connections in 31 real seconds ?



--
View this message in context: 
http://openssl.6102.n7.nabble.com/OpenSSL-s-time-output-meaning-tp67092.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users