Re: Compression of rolled files : performance issue when lots of JVMs are using timed based policy

Hi Remko My first idea was to have the rolling that triggers at the expected time, and the compression that will be delayed. That's why I wanted the delayed compression to occur before shutdown since the rolling already occurred. But I think that's a bad idea. First, it will lead to "fancy code"

Re: Compression of rolled files : performance issue when lots of JVMs are using timed based policy

Ok, I will open a jira ticket and provide a PR. Thanks for your input. Le 23 mars 2017 13:08, "Remko Popma" a écrit : > I see what you mean now. I agree it's better to keep the rollover concept > to mean file rename and compression that happen in sequence together. So >

Re: Compression of rolled files : performance issue when lots of JVMs are using timed based policy

I see what you mean now. I agree it's better to keep the rollover concept to mean file rename and compression that happen in sequence together. So the randomization affects when the _sequence_ is triggered, not just one part of the sequence. Makes sense. Sent from my iPhone > On Mar 23,

Re: Compression of rolled files : performance issue when lots of JVMs are using timed based policy

https://issues.apache.org/jira/browse/LOG4J2-1855 https://github.com/apache/logging-log4j2/pull/68 Let me know if you want me to do some changes Regards, Anthony 2017-03-23 13:15 GMT+01:00 Anthony Maire : > Ok, I will open a jira ticket and provide a PR. > > Thanks