From: Jaap S. <j....@hc...> - 2004-05-13 01:04:10
|
Bruce Sherwood wrote: > Oops! I made a mistake. The 1% was with Jonathan Brandmeyer's new (but > still somewhat experimental) Boost-based VPython. When I run the older > Visual-2003-10-05 (the latest nonexperimental version) on a 1.4 GHz > laptop, I see 40% CPU with lathe.py and 20% CPU with stonehenge.py (odd > that stonehenge uses less CPU than lathe). > > The renderer thread does sleep, so you won't see 100% utilization. > > Bruce Sherwood > > Kuzminski, Stefan R wrote: > >> Hmm, Stonehenge takes ~20% of the cpu on my XP laptop. The date at the >> top of __init__.py is "Visual-2003-10-05". Perhaps I will try a more >> recent release. >> >> If that renderer thread doesn't sleep at some point in its loop, it will >> consume a lot of CPU just looping, but usually that behavior is to use >> 100% of the CPU. >> >> thanks, >> S With the same Visual-2003-10-05 I get 99% CPU for pythonw.exe executing bounce2.py on my 2.7 GHz XP laptop. Starting an other session they share the CPU cycles 50% resp. 49%. Jaaop Spies |