Misleading memory consumption bar chart

[cornerman]

The readme shows a bar chart comparing memory consumption of scribe and scala logging. As the y-axis is cut off at some arbitrary value (590... which unit btw?),i it makes the difference seem enormous while in reality it is much smaller.

I really like this library and the performance information provided is nice, but I think we should show the data in an honest way. When recommending the library to other people, I already got negative feedback about this chart. Can we change this?

[darkfrog26]

I don't disagree with you, but there wasn't any malicious intention behind it. I simply plugged the values into a chart generator and that's how it represented the values. If you'd like to provide alternative graphs I'd happily replace them. I believe it was https://www.onlinecharttool.com/ that I used.

[darkfrog26]

Is this a more representative image? I'm going to be releasing Scribe 2.0 this week and want to make sure the visualizations (coming from JMH) don't come across as misleading.

[cornerman]

@darkfrog26 Nice! The numbers look very good, too. Did something significantly change? And where is scibe-async coming from? :)

[darkfrog26]

Scribe 2.0 (you can see it in the "2.0" branch) is a complete re-write of Scribe with a focus on performance. It also adds a "scribe-extras" module for asynchronous write operations (since it adds a dependency to Akka).

[darkfrog26]

Scribe 2.0 has been released and all new charts and graphs have been created. Please confirm you agree these are in no way misleading and close this ticket. Thanks!

[cornerman]

Great and now I am really looking forward to trying out the new release!

Thanks for taking care of this :)