Logging config dramatically impacts throughput

[Cantor, Scott]

On 9/28/15, 10:58 AM, "dev on behalf of Marvin Addison" <dev-bounces at shibboleth.net on behalf of marvin.addison at gmail.com> wrote:

>I wanted to report a surprising finding from load testing the past couple days. I was testing against our dev environment where we log net.shibboleth.idp at DEBUG, which as you know generates a mountain of output. I happened to turn it down to INFO and noticed a 2-8x increase in throughput. The effect was not surprising, of course, but the magnitude was shocking.

That's generally been true since V2 (probably was true before, but back that far there were signing bottlenecks anyway).

>I'm sure no one will run the IdP with noisy categories at DEBUG for any extended period of time, so it's probably not relevant in general. That said, it costs virtually nothing to wrap IDP_PROCESS in an async wrapper to prevent potentially serious degradations in performance when DEBUG logging is enabled for troubleshooting.

Not familiar with that particular feature. Is it new?

-- Scott