Ticket #716 (closed defect: worksforme)

Opened 11 years ago

Last modified 9 years ago

Firefox writes entirely too much to AFS homedirs

Reported by: jdreed Owned by:
Priority: normal Milestone: Precise Beta
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:

Description

Firefox becomes unusable when there's a network outage, because it spends way too much of its time writing stuff to .mozilla for every URL it loads.

This causes users to assume that Firefox and/or Debathena sucks. And arguably, Firefox does. However, I assert that we can turn cacheing off by default, because it's 2010 and the network is rarely the bottleneck for HTTP traffic. I don't think we can decide to turn history off for users, but there's got to be something we can do.

Change History

comment:1 Changed 11 years ago by xavid

How about doing something cool with symlinks to move the caching to /tmp/?

comment:2 Changed 11 years ago by rbasch

Our extension sets the cache directory to be under /var/tmp.

comment:3 Changed 11 years ago by jweiss

It has been a requirement from ops that the user's cache not be in AFS by default approximately forever. As Bob notes our extension takes care of this. I believe our options are either to try to move some of the large DBs out of the users profile (which probably violates least surprise, since I'll bet users expect firefox to remember those things across sessions) or to close this as WFM.

comment:4 Changed 11 years ago by jdreed

  • Milestone changed from The Distant Future to Natty Beta

Firefox, with about a month's worth of browsing history, on a 620 on a 10Mbit network is entirely unusable. We should do something clever with this ticket.

comment:5 Changed 11 years ago by jdreed

As noted on zephyr, someone should test FF4 and compare behavior.

comment:6 Changed 10 years ago by jdreed

  • Milestone changed from Natty Beta to Fall 2011

urlcalssifer3.sqlite is still stupidly large. Given that this doesn't vary on a per-user basis (Right? It's Google's malware db, or something?), can we do something awesome with symlinks?

I'm re-milestoning, since if symlinks don't work, I'm not convinced we can implement debathena-geofft-dot-mozilla-fuse-awesomeness-config in time.

comment:7 Changed 9 years ago by jdreed

Is this still an issue with FF 10+? I haven't heard anywhere near as many complaints.

comment:8 Changed 9 years ago by jdreed

  • Status changed from new to closed
  • Resolution set to worksforme

This seems significantly better with FF 10+. If it's not, re-open this with useful fixes. Keeping in mind #329 is a separate ticket.

Note: See TracTickets for help on using tickets.