djeter: Win32 2004-03-12 trunk (O2/GL6/SSE Optimized)
- bcool
- Posts: 638
- Joined: December 27th, 2003, 9:01 am
- Location: Ozarks
This is a nice build. It's strange that I seem to come out noticeably better on a couple of rendering tests by disabling accessibility.typeaheadfind. I saw in your .mozconfig extract on page 1 that "ac_add_options --disable-accessibility"(?) is indicated.
I guess I'm confused now as to what YOUR entry there is actually refering to then.
---
Intel PIII 1000
WINXP SP1
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040312 Firefox/0.8.0+ (djeter)
I guess I'm confused now as to what YOUR entry there is actually refering to then.
---
Intel PIII 1000
WINXP SP1
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040312 Firefox/0.8.0+ (djeter)
Last edited by bcool on March 13th, 2004, 6:35 am, edited 4 times in total.
Never let them see you sweat
- whiskydean
- Posts: 36
- Joined: March 12th, 2004, 9:00 am
bcool wrote:This is a nice build. It's strange that I seemed to come out better on a couple of rendering tests by disabling accessibility.typeaheadfind. I saw in your .mozconfig that ac_add_options --disable-accessibility is indicated. I guess I'm confused what this actually refers to then.
disabling accessibility.typeaheadfind is faster for me too, using
http://scragz.com/tech/mozilla/test-rendering-time.php
--- P3 - 650mhz - w2k sp4 ---
-
- Posts: 11
- Joined: March 5th, 2004, 4:16 pm
whiskydean wrote:disabling accessibility.typeaheadfind is faster for me too, using
http://scragz.com/tech/mozilla/test-rendering-time.php
--- P3 - 650mhz - w2k sp4 ---
went from 40.2 to 37.0 by disabling it... still don't know what it actually did
--- P3 - 1.1 ghz - win .net svr sp0 ---
- whiskydean
- Posts: 36
- Joined: March 12th, 2004, 9:00 am