“In those seven years that I’ve worked for Magnolia, I think I didn’t have a day where I didn’t like to work. And I think that’s special.” 🌟
- Anja, Product Design Lead at Magnolia
Check out our new page to meet our Product Development team 👉 https://t.co/43xBgVma5d
Ever wondered what a DXP is and what it can do for you? 😨
If your answer is yes ✅, you should check out our latest white paper written for marketers 👉 https://t.co/ppBrW6gwwU
#magnoliacms#magnoliadxp#dxp#dx#composable
A Bottle of water can be .50 cents at a supermarket. $2 at the gym. $3 at the movies and $6 on a plane. Same water. Only thing that changed its value was the place..So the next time you feel your worth is nothing, maybe you’re at the wrong place💯
#Logback version 1.3.0 and 1.4.0 have been released.
To make life easier for our users, logback 1.3.x will support Java EE whereas logback 1.4.x will support Jakarta EE, otherwise the two versions will be feature identical.
See also https://t.co/kkO8qImCqj
@DaschnerS@ceki@yazicivo So the title of your post is a bit misleading: you are not comparing logging frameworks but the performance of various *configs* you found in different projects. I think you should state this more clearly upfront to avoid confusion.
@DaschnerS@ceki@yazicivo I made a quick test on my machine after adding timestamp and lock to the console and disabled immediate flushing on the file appender. Here are the numbers now:
quarkus stdout: 139.7 req/s
logback file: 1456.12 req/s
@DaschnerS@ceki@yazicivo I'm also quite surprised by these numbers... and honestly the stdout scenario vs other logging options doesn't seem fair to me. (1/n)
@DaschnerS@ceki@yazicivo Third: file logging is configured with immediate flush forcing an IO sync after each event. Console output is usually buffered. To be fair, file logging should not flush immediately...
@DaschnerS@ceki@yazicivo Second: access to the console does not seem to be guarded by a lock to coordinate concurrent accesses. I'm not a Quarkus guru, could be the Quarkus console is already thread safe...