cfbolz changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://botbot.me/freenode/pypy/ ) | use cffi for calling C | mac OS and Fedora are not Windows
<dstufft> I don't really know how to narrow this down, however I have a branch were I'm trying to switch PyPI/Warehouse over to PyPy3. Using the PyPy3-6.0.0 (from docker if it matters) my tests run in a ~reasonable amount of time (5x slower than CPython, what I expected). If I try to download the nightly release (http://buildbot.pypy.org/nightly/py3.5/pypy-c-jit-95315-0a5cd8d36e99-linux64.tar.bz2) the tests are REALLY slow
<dstufft> like I got 19% way through running them, and it got mad and canceled it
<dstufft> and that was 20 minutes (instead of 200s, which is the PyPy3-6.0.0 runtime)
<dstufft> I was also having problems where the tests seemed to just randomly hang, although I can't tell if it was hanging or just doing something really slow (but if that's the case, it only sometimes happened)
<dstufft> I don't really know what to do about ^, I don't have nearly enough expertise in PyPy to even really know how to debug something like that... I assume it's not expected? Or do the nightlies act like that?
<njs> dstufft: fwiw, it's not a universal problem with the nightlies, e.g. here's a random recent run of trio's test suite: https://travis-ci.org/python-trio/trio/builds/453807815
<njs> running the tests on pypy is ~3x slower than cpython, but the release version, 3.5 nightly, and 3.6 nightly are all about the same
adamholmberg has joined #pypy
<dstufft> Yea, I expected the CPython -> PyPy slowdown
<dstufft> which was 40s -> 200s or so
<dstufft> but the PyPy3-6.0.0 -> Nightly slow down was 200s to 1114s before I killed it at ~19%
<njs> I guess one way to narrow it down would be to try a few different nightlies and see if it happens consistently
<dstufft> yea i guess that'll be my next step
<njs> you could even grab a nightly from around the time of th elast release, and if that doesn't have the issue then you could bisect it :-)
<njs> vmprof might give you some insight into where all that extra time is going too
<dstufft> well the nightly I used has a red thing next to it
<dstufft> and this nightly has a green thing next to it
<dstufft> maybe that matters!
<dstufft> Ok neat
lritter has quit [Ping timeout: 264 seconds]
lritter has joined #pypy
lritter has quit [Ping timeout: 252 seconds]
dddddd has quit [Remote host closed the connection]
moei has joined #pypy
forgottenone has joined #pypy
Garen_ has quit [Read error: Connection reset by peer]
Garen has joined #pypy
fryguybob has quit [Read error: Connection reset by peer]
fryguybob has joined #pypy
forgottenone has quit [Read error: Connection reset by peer]
forgottenone has joined #pypy
glyph has quit [Quit: End of line.]
glyph has joined #pypy
glyph_ has joined #pypy
glyph has quit [Ping timeout: 268 seconds]
glyph_ is now known as glyph
lritter has joined #pypy
antocuni has joined #pypy
antocuni has quit [Remote host closed the connection]
forgottenone has quit [Ping timeout: 240 seconds]
adamholmberg has quit [Remote host closed the connection]
adamholmberg has joined #pypy
adamholmberg has quit [Remote host closed the connection]
adamholmberg has joined #pypy
adamholmberg has quit [Ping timeout: 245 seconds]
Garen has quit [Read error: Connection reset by peer]
Garen has joined #pypy
Garen has quit [Read error: Connection reset by peer]
Garen has joined #pypy
dddddd has joined #pypy
lritter has quit [Ping timeout: 268 seconds]