trentnelson

37 ms·

301.
by trentnelson 12y ago
Quickly scanned both those papers -- they look very interesting, I look forward to reading both in detail.
302.
by trentnelson 12y ago
> People need more performance, particularly multicore performance. Traditional Python supporters can put their head in the sand about this if they want, but these highly-performant new languages have clearly found a niche among Python f
303.
by trentnelson 12y ago
So, I have actually spent a lot of time thinking about these exact problems, but it would have been too overwhelming to try include that information in this initial deck. I'm not even sure if I can adequately summarize it here :-) (I&#
304.
by trentnelson 12y ago
^^^ what turnersr said. (Spot on, by the way.)
305.
by trentnelson 12y ago
Ah, I just reviewed the slides... looks like I don't actually mention __readfsbase(), I thought I did. Basically, on amd64, you can just read the base address of one of the FS/GS segment registers and that'll be guaranteed t
306.
by trentnelson 12y ago
You're right, even if you're still running efficiently on all cores, it's still Python. I actually make this exact point in a separate presentation that I did a few weeks ago: https://speakerdeck.com/trent&#x
307.
by trentnelson 12y ago
If you want to see me try get through 153 slides in 45 minutes (and fail), this talk was recorded here: http://vimeo.com/79539317 . There's a more recent but slightly shorter deck that focuses more on the general concur
308.
PyParallel: How we removed the GIL and exploited all cores(speakerdeck.com)
170 points by trentnelson 12y ago|85 comments