Java 8 should certainly be the base line supported version for the next version. We can use Java 6 for a sort of snapshot in time of what we have already, then begin work toward Chainsaw 3.0.
On 15 October 2017 at 14:23, Ralph Goers <ralph.go...@dslextreme.com> wrote: > Java 8 also has a replacement for SimpleDateFormat that should perform > much better than SimpleDateFormat. > > Ralph > > > On Oct 15, 2017, at 12:10 PM, Matt Sicker <boa...@gmail.com> wrote: > > > > On 14 October 2017 at 23:34, Scott Deboy <scott.de...@gmail.com> wrote: > > > >> Parsing time strings to their numeric values using SimpleDateFormat is > >> painfully slow - I don't even use it any longer when I'm looking at > >> 1M+ rows in Chainsaw. > >> > > > > For the JSON and binary formats, we can output timestamps as millis, so > > that'll parse really fast. :) > > > > > >> Implementation wise I wrote this in the heyday of Logrj1, so > >> LoggingEvent and a few other features of Log4j1, a number of which > >> aren't present at all in log4j2, are found throughout the code. > >> > > > > I was thinking that we might need to modularise Chainsaw a bit for that. > A > > core, log4j2, log4j1(?), logback, whatever really, and a UI module or two > > (depending on how the GUI evolves). I'll detail my ideas more thoroughly > as > > I plan out a general upgrade path. > > > > > >> A json receiver would be great! > >> > > > > I think so too. It's one of the lower overhead formats to parse right now > > until we have some avro/thrift ones. > > > > > >> Me, I've been working on a private cloud IaaS implementation for a few > >> years now - almost no Java there. > >> > > > > So if I had to guess, I'd say: Go, Ruby, Python? > > > > -- > > Matt Sicker <boa...@gmail.com> > > > -- Matt Sicker <boa...@gmail.com>
