On Fri, Jun 02, 2006 at 07:44:07PM -0400, Tim Peters wrote: > Fortran code could scream. Test times were reproducible to the > nanosecond with no effort. Running on a modern box for a few > microseconds at a time is a way to approximate that, provided you > measure the minimum time with a high-resolution timer :-) On Linux with a multi-CPU machine, you could probably boot up the system to use N-1 CPUs, and then start the Python process on CPU N. That should avoid the process being interrupted by other processes, though I guess there would still be some noise from memory bus and kernel lock contention. (At work we're trying to move toward this approach for doing realtime audio: devote one CPU to the audio computation and use other CPUs for I/O, web servers, and whatnot.) --amk
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