Closed
Bug 108388
Opened 24 years ago
Closed 24 years ago
Caching of DNS entries has stopped working
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
VERIFIED
WORKSFORME
mozilla0.9.7
People
(Reporter: verbal, Assigned: gordon)
Details
(Keywords: perf, regression)
I dont know when this stopped working but within the last couple months i have
noticed no difference in speed after going to a site again a second time (as you
should see a slower lookup time on the first and almost none on the 2nd).
I always thought this was my imagination but the last couple days i have been
having DNS lookup problems on the server side with it sometimes responding and
sometimes not (and it happens in all my apps so i know its not just mozilla).
After the first time it resolves the 2nd time doesnt resolve (even though it
should be cache).
This slows down performance a lot.
| Reporter | ||
Updated•24 years ago
|
Keywords: perf,
regression
When I set breakpoints on the code responsible for initiating dns lookups, I only
see one lookup per domain initiated for large sites such as www.cnn.com and
www.usatoday.com. Also, I can reload and shift-reload with no dns lookups
initiated at all.
It seems to still be working. Have you added a line to your prefs that might
have disabled it? The relevant prefs are:
"network.dnsCacheEntries"
"network.dnsCacheExpiration"
If they do not exist the defaults are network.dnsCacheEntries=32 and
network.dnsCacheExpiration=300 (seconds).
Marking WORKSFORME.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•