Closed Bug 501487 Opened 17 years ago Closed 15 years ago

Weave is slow on Flash drives

Categories

(Firefox :: Sync, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX
Future

People

(Reporter: mobrien118, Unassigned)

Details

(Whiteboard: [closeme 2010-11-15])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 GTB5 (.NET CLR 3.5.30729) Build Identifier: 0.4 Weave works well, but is very slow on Flash drives. I wonder if the code could be optimized to run more in memory, especially when doing version comparisons for updates. A reason why I ffel this is important is because Portable Firefox installations are a VERY GOOD use case for Weave.I would love to be on another continent and be able to pop in my USB drive and be using my same firefox settings, bookmarks and passwords as I do back home on my desktop. I'm sure others would too! Reproducible: Always Steps to Reproduce: 1. Install Firefox from PortableApps.com or other portable source 2. Install Weave 3. Log in and start a sync 4. Wait for a VERY long time to accomplish a sync and experience extreme overall Firefox slowdown every time a sync is performed. Actual Results: I had to wait a long time for the sync to complete and there was VERY high disk usage on the flash drive during the process. Expected Results: Gone a bit faster. It would be very nice if it did.
Component: General → Needs Triage
QA Contact: general → needstriage
Component: Needs Triage → General
QA Contact: needstriage → general
Is this still an issue? I know we use less disk I/O than we used to, but it can still be an issue because of writing new data to permanent storage (because that's how Firefox works).
Component: General → Firefox Sync: Backend
QA Contact: general → sync-backend
Target Milestone: --- → Future
reporter, is this still an issue?
Whiteboard: [closeme 2010-11-15]
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.