<snip> 
> Having a well defined test case (or set of test cases ... day 
> vs. night, 3d clouds, shadows) is definitely important to 
> having some sort of validity to the results.  Benchmarking 
> complex computer applications is not a fixed science.  There 
> are just way too many variables.  Assuming we haven't scared 
> off Paul from the task, my suggestion is to try to strike a 
> balance between enough simplicity to make the task managable, 
> and enough complexity to make the results useful.  The 
> results don't have to be perfect to be useful.
> 
> Perhaps there could be an optional 'notes' field for a 
> variety of special case comments to handle some of the 
> nuances that are outside the core test case(s).
> 
> Here we could make note if a particular video chipset or card 
> has abysmal performance, or if some combination of things 
> just don't work.  
> That would be a useful tool when/if people shop for new hardware.
> 
> Curt.
<snip> 

I don't know if the FlightGear Live-CD
(http://mail.flightgear.org/pipermail/flightgear-users/2004-January/0068
94.html) is still in existance, or being maintained, but this would be
an ideal way of benchmarking different hardware. Obviously it isn't
going to give you information about Windows/Linux changes.

My memory tells me that someone started to collect performance data
based on one of the Live-CD versions, but I cannot find it in the
archives, and I know that my memory plays tricks on me...

Richard

________________________________________________________________________
This e-mail has been scanned for Bede Scientific Instruments for all 
viruses by Star Internet. The service is powered by MessageLabs. For
more information on a proactive anti-virus service working around the
clock, around the globe, visit: http://www.star.net.uk
________________________________________________________________________

_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to