> Why are you surprised? Python is a very, very slow language. My very simple
> unoptimized C++ parsing code is more than 10x faster than Stem (parsing from
> memory). Go has some nice string parsing features, so zoossh should have an
> easy time to get fast and simple parsing code.
Because wit
On Sun, Aug 16, 2015 at 02:44:40PM -0700, Damian Johnson wrote:
> >> > Ideally, zoossh should do the heavy lifting as it's implemented in a
> >> > compiled language.
> >>
> >> This is assuming zoossh is dramatically faster than Stem by virtue of being
> >> compiled. I know we've discussed this befo
> > zoossh's test framework says that it takes 36364357 nanoseconds to
> > lazily parse a consensus that is cached in memory (to eliminate the I/O
> > bottleneck). That amounts to approximately 27 consensuses a second.
> >
> > I used the following simple Python script to get a similar number for
>