Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

morepypy.blogspot.com

Post reply on HN
Print view View original

21–30 of 150 posts

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#21

Post by fijal »

gdulli wrote: post #19

My experience with PyPy was that it was faster for mapreduce jobs without JSON parsing and slower for JSON-heavy jobs. Because, I assume, CPython benefits from a C implementation of simplejson and PyPy doesn't. Does anyone know if this has changed? (I'll probably install 4.0 and see for myself, but curious if anyone knows what I should expect.)

We did put some effort into making built-in json faster. If you're using an optimized version like uJson, it'll be faster under cpython so far, but it all depends whether there is more processing or more parsing involved. We're happy to help you with benchmarks though

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#22

Post by baq »

upofadown wrote: post #15
baq wrote: post #7

python 3.4 please ;_;

The value of PyPy is that it is a thing you can just drop in to make your code faster. If PyPy wants to gain any traction they pretty much have to concentrate on the version with the most existing code.

most of my existing production code is 3.4, hence my question.

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#24

Post by MrBuddyCasino »

ragebol wrote: post #12
MatthewWilkes wrote: post #9

> We would also like to thank our contributors (7 new ones since PyPy 2.6.0) and encourage new people to join the project. PyPy has many layers and we need help with all of them This doesn't match my experience of the PyPy project. I found a tiny bug in the stdlib matching against CPython, went into IRC to ask a question about test running to be sure I got it right and was quickly engaged in conversation about why I…

Is this a complaint or a compliment to the developers?

He didn't want to report a bug, he wanted to contribute to the project. I can think of a few reasons why. They lost a new potential committer by "being pragmatic" about it, but ignoring inter-personal relationships, like so often.

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#25

Post by forgotpwtomain »

MrBuddyCasino wrote: post #24
ragebol wrote: post #12

Earlier quoted context omitted.

Is this a complaint or a compliment to the developers?

He didn't want to report a bug, he wanted to contribute to the project. I can think of a few reasons why. They lost a new potential committer by "being pragmatic" about it, but ignoring inter-personal relationships, like so often.

Personally I'd be quite excited to see a bug I reported fixed the same-day - of course people's expectations are different it's not always easy to balance these things.

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#26

Post by gdulli »

fijal wrote: post #21
gdulli wrote: post #19

My experience with PyPy was that it was faster for mapreduce jobs without JSON parsing and slower for JSON-heavy jobs. Because, I assume, CPython benefits from a C implementation of simplejson and PyPy doesn't. Does anyone know if this has changed? (I'll probably install 4.0 and see for myself, but curious if anyone knows what I should expect.)

We did put some effort into making built-in json faster. If you're using an optimized version like uJson, it'll be faster under cpython so far, but it all depends whether there is more processing or more parsing involved. We're happy to help you with benchmarks though

I've only used simplejson. A mapreduce job could be reading billions of lines and possibly doing very simple logic on each line, so the parsing/encoding is a big percentage of the processing, sometimes nearly all of it. I'll try 4.0 and see how it does now.

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#27

Post by fijal »

gdulli wrote: post #26
fijal wrote: post #21

Earlier quoted context omitted.

We did put some effort into making built-in json faster. If you're using an optimized version like uJson, it'll be faster under cpython so far, but it all depends whether there is more processing or more parsing involved. We're happy to help you with benchmarks though

I've only used simplejson. A mapreduce job could be reading billions of lines and possibly doing very simple logic on each line, so the parsing/encoding is a big percentage of the processing, sometimes nearly all of it. I'll try 4.0 and see how it does now.

Try builtin json instead of simplejson for pypy (it's API-equivalent)

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#29

Post by wyldfire »

dr_zoidberg wrote: post #17
pjmlp wrote: post #8

Earlier quoted context omitted.

> But bottom line, tons of python code out there needs more performance and has no dependency on numpy or any C extensions. What they need is nice JIT engines like PyPy and not to switch languages. If no one invested in improving implementations for modern languages and switched to something lower level all the time, we would still be using Fortran for business applications.

I think you guys are saying the same thing. Ie, because they don't need to switch languages, and PyPy is a JIT engine for Python, these tons of Python code would benefit from if the devs were aware of PyPy .

Indeed that's what I meant and perhaps pjmlp thinks that the feature set in numpy could have been / could be implemented in pure python, now that we have PyPy.

Re: PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More

#30

Post by wyldfire »

fijal wrote: post #6
wyldfire wrote: post #5

Kudos to the pypy team! I suspect pypy would benefit from some kind of marketing campaign. It rarely lets me down and yet lots of python devs don't know about it. The most popular package(s) that don't work with it have been numpy, scipy, etc. When I first encountered pypy, there was a numpypy and I wouldn't be surprised if that's different now. But bottom line, tons of python code out there needs more performance an…

we're trying to address both numpy and C extensions, stay tuned ;-)

Keep up the good work!
Post reply on HN