JUL bridge generates a lot of unnecessary data

[andrzejressel]

Currently due to ".level = ALL" in Jul config all logs go to zio. I was expecting some kind of overhead, but not too much. When profiling my JAXB app, 20% of deserialization time and 90% of memory usage is wasted due to pushing FINEST level logs.

I guess current api has to be deprecated and every method should also have parameter with JUL config.

[justcoon]

hi @andrzejressel
this seems to be similar problem like #809, which was solved with #810, and also jul-bridge have similar support

so if this is something like that, than it should be possible to set LogFilter for jul-bridge as mentioned in docs

[andrzejressel]

Yeah, that seems to fix the issue. I think I will deprecate initialize and add note about finest level.