Difference between revisions of "Talk:3Dfps"
(templates on dynamic page done) |
(Broken redirect) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 14: | Line 14: | ||
Layout: | Layout: | ||
| − | * First part as a template (to be editable by the public): Template:Benchmarks_Header | + | * First part as a template (to be editable by the public): [[Template:Benchmarks_Header]] |
* Dynamic database-driven table with sorting | * Dynamic database-driven table with sorting | ||
| − | * Lats part as a template again (for notes): Template:Benchmarks_Footer | + | * Lats part as a template again (for notes): [[Template:Benchmarks_Footer]] |
| − | Further discussion on the new dynamic benchmark page on Template:Benchmarks_Header, please! | + | Further discussion on the new dynamic benchmark page on [[Template:Benchmarks_Header]], please! |
--[[User:Akw|akw]] 21:57, 8 Oct 2004 (CEST) | --[[User:Akw|akw]] 21:57, 8 Oct 2004 (CEST) | ||
| + | ---- | ||
| + | |||
| + | == how to run instructions needed == | ||
| + | |||
| + | I think we need instructions on how to run the benchmark. | ||
| + | |||
| + | For instance it is not clear if the benchmark should just be started from the cmdline and have it run with default window size, or if it should be resized to fullscreen. | ||
| + | |||
| + | For instance I am running Fedora Core 3T2 with x.org 6.8.1 and am getting 1067 FPS with the default window size, but only 92 FPS at fullscreen. | ||
| + | This is on a T30 (2366-52U) which has a 1.8GHz P4M, running the opensource radeon driver. | ||
| + | |||
| + | == Broken redirect == | ||
| + | |||
| + | The redirect is currently broken. | ||
| + | |||
| + | Which is just as well -- glxgears is '''not a valid benchmark'''. It was not intended to be one, and the workload it generates on modern cards is totally different from any realistic X app (heck, I get better glxgears FPS when I ''disable'' hardware acceleration). Please stop using it. | ||
| + | |||
| + | --[[User:Thinker|Thinker]] 15:57, 28 November 2006 (CET) | ||
---- | ---- | ||
Latest revision as of 15:57, 28 November 2006
(for discussion of formatting, see history -- Nomeata)
Shoudn't the kernel be after the driver, since I'd rather compare different kernels and same driver than different driver and same kernel? --Nomeata 13:25, 29 Sep 2004 (CEST)
I think one more often compares different drivers at same kernels. Also i think that driver variation will be more than kernel variation. However, i'd suggest the following order: Model, Benchmark, Driver, fps, XServer, Kernel, Notes, User. This would represent the following search pattern: "Ok, i have a T41p, i'm using the fglrx driver and glxgears seems a bit slow to me, lets have a look... ahh...100 fps more...why...ahh...XServer is more recent...kernel is less recent (does that matter?)...ohh...and i should probably check my mtrr."
Wyrfel 13:57, 29 Sep 2004 (CEST) 13:56, 29 Sep 2004 (CEST)
I coded a new MediaWiki Specialpage, to get the table dynamic (to be database-driven, enabling sorting and so on). It is not yet finished. Hope I will get this finished soon. The MediaWiki code is strange and rather poorly documented. Suggestions are appreciated! :-)
Layout:
- First part as a template (to be editable by the public): Template:Benchmarks_Header
- Dynamic database-driven table with sorting
- Lats part as a template again (for notes): Template:Benchmarks_Footer
Further discussion on the new dynamic benchmark page on Template:Benchmarks_Header, please!
--akw 21:57, 8 Oct 2004 (CEST)
how to run instructions needed
I think we need instructions on how to run the benchmark.
For instance it is not clear if the benchmark should just be started from the cmdline and have it run with default window size, or if it should be resized to fullscreen.
For instance I am running Fedora Core 3T2 with x.org 6.8.1 and am getting 1067 FPS with the default window size, but only 92 FPS at fullscreen. This is on a T30 (2366-52U) which has a 1.8GHz P4M, running the opensource radeon driver.
Broken redirect
The redirect is currently broken.
Which is just as well -- glxgears is not a valid benchmark. It was not intended to be one, and the workload it generates on modern cards is totally different from any realistic X app (heck, I get better glxgears FPS when I disable hardware acceleration). Please stop using it.
--Thinker 15:57, 28 November 2006 (CET)
