From: Gary R. <gr...@bi...> - 2009-02-21 00:19:23
|
I think Bruce meant the following to go to the list (sorry Bruce if it wasn't): -- Actually, it was also the case in Visual 3 that setting the rate too high could slow down the animation loop. Probably depends on the details of the particular program. It would be useful for those interested in these issues to post relatively simple examples with compute times, and say what the hardware/software environment is. The standard scheme looks like this: from time import clock .... t = clock() .....Do Computations t = clock()-t print t Make more than one run with a program and average the results because you'll observe fluctuations, presumably associated with other random stuff the operating system is doing. In my own measurements of this kind I've seen little difference between Visual 3 and Visual 5. Bruce Sherwood Gary Ruben wrote: > I haven't checked this carefully but I had the impression on my > system that 5.0 was slower too, especially with examples like > drape.py but that playing with the value in any rate() calls affects > this. The rate function in 3.0 used to behave as advertised. In 5.0 > it seems to me that setting it too high actually slows down the > animation loops. > > Gary R. > > > Stef Mientki wrote: >> hello, >> >> I tried the same program on another system today, which should be >> faster than the system I used yesterday (faster processor, Intel >> instead of AMD, faster (external) graphics card), >> but it seems to be about twice as slow as my yesterday system. On >> that theoretical faster but in practice slower system, indeed the >> performances are about equal for VP3 and VP5 ??? >> >> cheers, Stef |