--
You received this message because you are subscribed to the Google Groups "Java Chronicle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to java-chronicl...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hello PeterI have been able to log text via chronicle 3 using vanilla configs. The Garbage generation from logger has been reduced drastically. But as a final step i find excerpts are getting prefixed with octals 177775 177777. What would be your suggested solution to eliminate these bytes.
On Monday, February 24, 2014 9:58:08 PM UTC+5:30, Peter Lawrey wrote:I have a concurrent VanillaChronicle and it is lock free and can be shared across processes (in the sandbox area), but you should be aware that is not actually faster than IndexedChronicle.You can write text to Chronicle instead of binary (which is make more of a difference than using locking) but it is the end of the file which is padded and confuses some tool. The simplest approach is to use ChronicleReader (which can dump from an index) and dump this to text or grep the output.On 24 February 2014 13:49, Jatinder Singh <jatinder...@gmail.com> wrote:
Hello PeterI wanted a low gc solution for logging, which directed me to this awesome project. I would prefer to avoid synchronization/locks while using chronicle for logging.I wanted to ask if there is a better approach then to have chronicle as ThreadLocal variable and each thread writing to a separate file?Also is there a way to configure chronicle to output data file in text format instead of current binary one. (cat {filename} shows the text but less and other unix commands dont display messages properly)--To unsubscribe from this group and stop receiving emails from it, send an email to java-chronicl...@googlegroups.com.
You received this message because you are subscribed to the Google Groups "Java Chronicle" group.--
You received this message because you are subscribed to the Google Groups "Java Chronicle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to java-chronicl...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Java Chronicle" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/java-chronicle/tkHfm8Ogt10/unsubscribe.
To unsubscribe from this group and all its topics, send an email to java-chronicl...@googlegroups.com.
Not sure. It could be possible but this is not tested.
--
You received this message because you are subscribed to the Google Groups "Java Chronicle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to java-chronicl...@googlegroups.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Java Chronicle" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/java-chronicle/tkHfm8Ogt10/unsubscribe.
To unsubscribe from this group and all its topics, send an email to java-chronicl...@googlegroups.com.
Chronicle is designed to run in an environment without any collectipms incl minor. This sounds like a bug to me.