Closed Bug 234683 Opened 22 years ago Closed 5 years ago

Using no value for charset detect slows down Camino by 15%

Categories

(Core :: Internationalization, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mikepinkerton, Assigned: smontagu)

Details

Camino used to (wrongly) run with pref("intl.charset.detector", "universal_charset_detector"); Someone pointed out the error of our ways and i removed this line from all-camino.js, defaulting to whatever mozilla does. At this point (and you can see it if you look at Tp from the Pawn tinderbox in mid-Jan 2004), we took at 15% Tp hit. Just to be sure, I added the line back in this morning and we got 15% faster again. Why are we 15% slower not doing any detection?
Are you sure this is the right way round. We should be faster without "universal_charset_detector", no with it.
in the past (and maybe this changed since 0.7ish), not setting universal_charset_detector was the way to turn it on. yes, quite confusing, but that was what we did.
QA Contact: amyy → i18n

The detector has been rewritten.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.