Ian Molton wrote:
There are four times when the configuration file format would need to be processed.On Tue, 28 Jan 2003 01:25:48 -0600 (CST) "D. Hageman" <[EMAIL PROTECTED]> wrote:what alternative do you propose that would be faster? Are we talking seconds, minutes, hours ... what?
On some systems, every nanosecond counts.
1. When some utility (either a GUI configuration tool or just a "dump" utility) reads the list of available settings from the driver.
2. When some utility reads the configuration file to present the current settings to the user.
3. When some utility writes the configuration file.
4. When an OpenGL application starts. Specifically, the configuration file would be processed when the first GL context is created, which may not be immediatly when the application starts.
Of the four, only the fourth has performance requirements that cannot be measured using a stopwatch. Nanoseconds is too harsh of a metric, but there is certainly a reasonable limit to how much time we can spend processing a configuration file.
This sounds like a good case for a conformance test. We'll need to figure out, for a baseline platform, what upper-bound is for the time spent on a pathological config file. Coming up with a pathological case should be done sooner rather than later.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
