users@grizzly.java.net

Re: High CPU Usage on SSL utils

From: Oleksiy Stashok <oleksiy.stashok_at_oracle.com>
Date: Fri, 19 Jun 2015 19:18:19 +0200

Hi Tiran,

I see your concern, but IMO it's similar to what you found w.r.t.
"selector", if you enable "core classes" profiling - you'll see that
it's core SSL implementation consumes CPU, not Grizzly itself. Once you
have the profiling results with core classes, we can check what exactly
consumes that much time.

Thanks.

WBR,
Alexey.

On 18.06.15 20:07, Meltser Tiran wrote:
>
> Hi Alexey (working with Efrat and Uri) J,
>
> First we don’t keep the connections open as this is an IMAP server (or
> proxy).
>
> Second, I agree that SSL channel should have some performance price
> but what we experience is far beyond a reasonable price, after making
> another check we see we have response times slower *600* times than
> plain communication…
>
> Third, we are running on a 16 cores machine in which SSL should hardly
> be noticed.
>
> Forth, we have just compared the SSL experience to our previous server
> written in C++ some more than 10 years ago and operated on machines
> with about ¼ CPU power (or even less), and load results show response
> time was doubled at max (*not 600 times worse*).
>
> Can you have a look on the hot method the profiler is showing and see
> if something can be done there (or maybe give us some guideline)?
>
> *Tiran Meltser***
> System Architect
> Global Products & Operations
> *Comverse* – /Making Your Network Smarter/
>
> T +972-3-7678381
> M +972-54-5639381
> Tiran.Meltser_at_comverse.com <mailto:Tiran.Meltser_at_comverse.com>
> *www.comverse.com <http://www.comverse.com/> *
>
> *P****Please think of the environment before printing this email***
>
> *From:*Oleksiy Stashok [mailto:oleksiy.stashok_at_oracle.com]
> *Sent:* Thursday, June 18, 2015 8:16 PM
> *To:* users_at_grizzly.java.net
> *Subject:* Re: High CPU Usage on SSL utils
>
> Hi Efrat,
>
> do you keep connections alive?
> In general SSL is not for free and it's expected to be slower than
> plain communication.
>
> WBR,
> Alexey.
>
> On 18.06.15 18:14, Ben-Yosef Efrat wrote:
>
> Also, we see higher response times then before (around 50 times
> longer)
>
> *From:*Ben-Yosef Efrat [mailto:Efrat.Ben-Yosef_at_comverse.com]
> *Sent:* Thursday, June 18, 2015 6:54 PM
> *To:* users_at_grizzly.java.net <mailto:users_at_grizzly.java.net>
> *Cc:* Broide Uri; Meltser Tiran
> *Subject:* High CPU Usage on SSL utils
>
> Hi Alexey,
>
> Continuing Uri’s query about the CPU, we moved to java8 profiler
> and as you said, indeed not the select() was the issue.
>
> Now, we added the SSL to the picture (utilizing Grizzly’s
> SSLfilter) and as you can see in the attached screenshot, the
> executeDelegatedTask() method consumes a lot of CPU (we sort by
> self-tile CPU).
>
> Please advise,
>
> Thanks,
>
> Efrat
>
> cid:image001.png_at_01D0A9F5.776D0720
>
> ------------------------------------------------------------------------
>
> “This e-mail message may contain confidential, commercial or
> privileged information that constitutes proprietary information of
> Comverse Inc. or its subsidiaries. If you are not the intended
> recipient of this message, you are hereby notified that any
> review, use or distribution of this information is absolutely
> prohibited and we request that you delete all copies and contact
> us by e-mailing to: security_at_comverse.com
> <mailto:security_at_comverse.com>. Thank You.”
>
> ------------------------------------------------------------------------
>
> “This e-mail message may contain confidential, commercial or
> privileged information that constitutes proprietary information of
> Comverse Inc. or its subsidiaries. If you are not the intended
> recipient of this message, you are hereby notified that any
> review, use or distribution of this information is absolutely
> prohibited and we request that you delete all copies and contact
> us by e-mailing to: security_at_comverse.com
> <mailto:security_at_comverse.com>. Thank You.”
>
> ------------------------------------------------------------------------
> “This e-mail message may contain confidential, commercial or
> privileged information that constitutes proprietary information of
> Comverse Inc. or its subsidiaries. If you are not the intended
> recipient of this message, you are hereby notified that any review,
> use or distribution of this information is absolutely prohibited and
> we request that you delete all copies and contact us by e-mailing to:
> security_at_comverse.com. Thank You.”