if there's anything else I can do.
Cheers,
Brecht
On Wed, 05 Aug 2015 09:52:23 +0200, Maciej Fijalkowski
wrote:
Hi Brecht
We tried the strbuf with rinohtype and (after warmup) it's the speed
of cpython, which is bad.
investigating some more
On Sun, Mar 2, 2014 at 12:34 AM, Br
x27;s going on and I'm
> failing so far. Thanks for a valuable benchmark! And yes, we're
> working on improving the warmup time (ETA unknown though)
On Sun, 02 Mar 2014 17:01:32 +0100 Armin Rigo wrote
> On 1 March 2014 23:34, Brecht Machiels wrote:
> &
e
>interpreter (so you pay the price for JITting, while you also pay the
>prace for not having compiled assembler). That probably does not
>explain everything, but please don't use sys._getframe in production
>code if you want the JIT to be fast.
>
>On Sun, Mar 2
Hello,
I've managed to backport RinohType to Python 2 (took me only a couple of hours
thankfully).
Results on my Celeron T3000 (Arch Linux x86_64):
CPython 3.3.414 s
PyPy3 2.1.0-beta1 61 s
CPython 2.7.615 s
PyPy 2.2.135 s
If you want to give it a try (no external d
On Thu, 06 Feb 2014 01:18:17 +0100 Philip Jenvey wrote
>We’re aiming to put out another PyPy3 release fairly soon, what’s currently
>pending is re-enabling of the optimized machine sized int operations, which
>should be finished pretty soon.
Great. I'll give it a try as soon as it's
re.
>
> On Mon, Feb 3, 2014 at 11:53 PM, Brecht Machiels wrote:
> > Hello,
> >
> > I spoke to Romain and Armin at FOSDEM about the poor performance of PyPy
> > running my application, RinohType.
> >
> > I'm not sure I mentioned that RinohT
Hello,
I spoke to Romain and Armin at FOSDEM about the poor performance of PyPy
running my application, RinohType.
I'm not sure I mentioned that RinohType only runs on Python 3. Perhaps this can
partly explain the poor performance? Anyhow, here's how you can benchmark
RinohType:
git clone
