Skip to content
Fetching contributors…
Cannot retrieve contributors at this time
87 lines (55 sloc) 1.95 KB
0.13
====
* #12: Added space between message and time.
* #14: New FormattedStopWatch class to provide machine-readable StopWatches
* API now prefers microseconds all around
* Allows setting of the property file from the command line using
-Dspeed4j.properties=myfile.properties
* #13: PeriodicalLog now allows explicit mode settings, JMX_ONLY, LOG_ONLY,
QUIET or ALL.
* Improved output of PeriodicalLog to handle longer tags.
0.12
====
* Speed4j core now requires only Java 5. Added note about PeriodicalLog requiring
Java6. Thanks to Brad Fitz!
* Documentation fixes, again thanks to Brad!
0.11
====
* Improved Perf4j compatibility by adding StopWatch.getElapsedTime()
0.10
====
* Much improved memory management: The StopWatch queue size has now a maximum limit
(to prevent a case where a producer would just keep sending stuff that we couldn't
process fast enough). Also, the StopWatch queues are now emptied as quickly
as possible.
* Added new internal JMX attribute: "DroppedStopWatches" to monitor StopWatches
which are dropped when they can't fit in the queue.
* There's another new internal JMX attribute: "StopWatchQueueLength" which you
can use to directly monitor whether Speed4j is keeping up with the incoming
events.
* You can now shut up the PeriodicalLog logging by simply setting the slf4jLogName
to an empty string.
* PeriodicalLog now requires Java 6 for j.u.c.LinkedBlockingDeque. Speed4j can
only be used on Java 5 VM if PeriodicalLog is not used.
0.9
===
* Fixed NPE when the tag didn't get any data. (Fixes #5 and #6).
0.8
===
* Minor performance optimizations; uses less memory overall.
0.7
===
* Fixes issues #1 & #2, where the Collector Thread was misbehaving.
(Yay! First issues!)
0.6
===
* Improved thread safety in PeriodicalLog calculations.
0.5
===
* Fixed NPE during PeriodicalLog shutdown.
0.4
===
* Added 95th percentile calculation, courtesy of Jakarta Commons.
0.3
===
First official release, yay!
Jump to Line
Something went wrong with that request. Please try again.