2008/11/3 <skip at pobox.com>: > > >> I believe everyone here knows that. I believe what most people are > >> clamoring for is to make "full use of their multi-CPU resources in a > >> single process". > > Josiah> Which is, arguably, silly. As we've seen in the last 2 months > Josiah> with Chrome, multiple processes for a single "program" is > Josiah> actually a pretty good idea. > > I have no idea what Chrome is. Is it a CPU-intensive algorithm which can be > parallelized? It's Google webbrowser ;) Matthieu Brucher > Josiah> With the multiprocessing module in the standard library offering > Josiah> a threading-like interface, people no longer have any excuses > Josiah> for not fully exploiting their multiple cores in Python. > > Except for communication overhead caused by replacing shared memory with > I/O? > > Skip > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/matthieu.brucher%40gmail.com > -- Information System Engineer, Ph.D. Website: http://matthieu-brucher.developpez.com/ Blogs: http://matt.eifelle.com and http://blog.developpez.com/?blog=92 LinkedIn: http://www.linkedin.com/in/matthieubrucher
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4