News for hackers. Stuff that matters.
Re:Python 3 Q&A by a prolific core developer by seunosewa on Friday June 29, 2012 @12:24PM (#4177452)
No, that was just an example of a unexpectedly CPU-bound operation. My point was that you can't assume your Python program is not CPU-bound. Every time you have to do something non-trivial in Python, performance could become an issue.
Re:Python 3 Q&A by a prolific core developer by pwang on Friday June 29, 2012 @01:31PM (#4177830)
How do you know it's not memory I/O bandwidth bound? Just curious.
Re:Python 3 Q&A by a prolific core developer by scott_s on Friday June 29, 2012 @02:59PM (#4178412)
From the perspective of a Python program, being memory bandwidth bound is the same as being CPU bound: you have the GIL, your process is in the running state in the OS, and is currently executing on a core.

(I assume you mean truly mean bandwidth between main memory and the processor, and not to disk.)