Nicholas Leippe wrote:
>
> This may be opening a pointless can of worms,
> but, I'm really curious as to how to explain
> the behavior I'm seeing. Each time I run
> gears, it is perfectly consistent in it's
> speed (+/- .5 FPS) for that instance. But,
> each time I run gears, it is consistent around
> a different value that ranges from 718 all the
> way to 751 FPS. Why would it do this? What
> might be determining this rate and why is it
> so consistent each time, and why does it not
> vary in each instance all the way up to the
> fastest I've seen it can go (~751)?
>
> Some consecutive runs:
>
> >/usr/X11R6/bin/gears
> 3467 frames in 5 seconds = 693.4 FPS
> 3684 frames in 5.001 seconds = 736.653 FPS
> 3681 frames in 5 seconds = 736.2 FPS
> 3681 frames in 5 seconds = 736.2 FPS
> 3682 frames in 5.001 seconds = 736.253 FPS
> 3683 frames in 5 seconds = 736.6 FPS
> 3682 frames in 5 seconds = 736.4 FPS
> 3683 frames in 5 seconds = 736.6 FPS
> 3681 frames in 5.001 seconds = 736.053 FPS
>
> >/usr/X11R6/bin/gears
> 3583 frames in 5 seconds = 716.6 FPS
> 3653 frames in 5 seconds = 730.6 FPS
> 3651 frames in 5.001 seconds = 730.054 FPS
> 3656 frames in 5 seconds = 731.2 FPS
> 3655 frames in 5.001 seconds = 730.854 FPS
> 3655 frames in 5 seconds = 731 FPS
> 3650 frames in 5 seconds = 730 FPS
> 3653 frames in 5 seconds = 730.6 FPS
>
> >/usr/X11R6/bin/gears
> 3580 frames in 5 seconds = 716 FPS
> 3648 frames in 5 seconds = 729.6 FPS
> 3647 frames in 5 seconds = 729.4 FPS
> 3648 frames in 5 seconds = 729.6 FPS
> 3648 frames in 5.001 seconds = 729.454 FPS
> 3651 frames in 5 seconds = 730.2 FPS
> 3648 frames in 5 seconds = 729.6 FPS
>
> >/usr/X11R6/bin/gears
> 3617 frames in 5.001 seconds = 723.255 FPS
> 3683 frames in 5.001 seconds = 736.453 FPS
> 3684 frames in 5 seconds = 736.8 FPS
> 3684 frames in 5.001 seconds = 736.653 FPS
> 3683 frames in 5 seconds = 736.6 FPS
> 3683 frames in 5 seconds = 736.6 FPS
> 3680 frames in 5 seconds = 736 FPS
> 3682 frames in 5 seconds = 736.4 FPS
> 3682 frames in 5 seconds = 736.4 FPS
> 3684 frames in 5 seconds = 736.8 FPS
> 3685 frames in 5 seconds = 737 FPS
> 3681 frames in 5 seconds = 736.2 FPS
>
> >/usr/X11R6/bin/gears
> 3688 frames in 5 seconds = 737.6 FPS
> 3756 frames in 5 seconds = 751.2 FPS
> 3758 frames in 5 seconds = 751.6 FPS
> 3754 frames in 5 seconds = 750.8 FPS
> 3758 frames in 5.001 seconds = 751.45 FPS
> 3757 frames in 5 seconds = 751.4 FPS
> 3756 frames in 5 seconds = 751.2 FPS
>
> >/usr/X11R6/bin/gears
> 3644 frames in 5 seconds = 728.8 FPS
> 3716 frames in 5 seconds = 743.2 FPS
> 3714 frames in 5.001 seconds = 742.651 FPS
> 3717 frames in 5 seconds = 743.4 FPS
> 3717 frames in 5 seconds = 743.4 FPS
> 3716 frames in 5.001 seconds = 743.051 FPS
> 3717 frames in 5 seconds = 743.4 FPS
>
> >/usr/X11R6/bin/gears
> 3649 frames in 5 seconds = 729.8 FPS
> 3717 frames in 5 seconds = 743.4 FPS
> 3716 frames in 5.001 seconds = 743.051 FPS
> 3717 frames in 5 seconds = 743.4 FPS
>
> >/usr/X11R6/bin/gears
> 3522 frames in 5 seconds = 704.4 FPS
> 3591 frames in 5 seconds = 718.2 FPS
> 3596 frames in 5 seconds = 719.2 FPS
> 3596 frames in 5 seconds = 719.2 FPS
> 3595 frames in 5 seconds = 719 FPS
> 3593 frames in 5 seconds = 718.6 FPS
> 3593 frames in 5.001 seconds = 718.456 FPS
>
> This is not what I'd expect.
This isn't really unexpected. Benchmarking any application on
a time-sharing operating system can reveal some variation in
performance. You never know when another process or the kernel
itself will need some CPU cycles.
-Brian
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
