Re: ultralog: new concept of logging API
Mikhail Vladimirov wrote:
DUDE! Attribute quotes!
Please.
Arne wrote:
Any measurements of the impact for some realistic code?
The idea that high-performance application may want to process data witho=
ut producing garbage is not something new. Check, for example, this link: =
http://oreilly.com/catalog/javapt/chapter/ch04.html
The same could be said about lock-free design. It is well known approach=
to increase performance of multi-threaded applications.
Ultralog is not the first Java library designed to be garbage- and lock-f=
ree and focused on demands of high performance applications. See, for exam=
ple, LMAX Disruptor: http://lmax-exchange.github.com/disruptor/ It is all =
about hot to avoid lock and garbage creation and it states itself as "High =
Performance Inter-Thread Messaging Library".
Ultralog is even not the first attempt to create garbage-free logging fra=
mework for Java. See, for example, the following link: https://bitbucket.o=
rg/vladimir.dolzhenko/gflogger/wiki/Home It states its goal as "to create =
ad-hoc logger for low latency (latency critical) applications (to be precis=
e for latency critical execution path) which will affect application explic=
it and implicit (though gc pauses) as less as it possible". It does not cl=
aim itself to be lock-free though.
What is new in ultralog in comparison with gflogger, is that it demonstra=
tes that garbage-free logging could be done without sacrificing code readab=
ility.
In other words, no, no measurements.
--
Lew