Closed Bug 601994 Opened 14 years ago Closed 14 years ago

Startup of Weave is terribly slow.

Categories

(Cloud Services :: General, defect, P2)

Product:
Cloud Services
Component:
General
Type:
defect

Tracking

(fennec2.0+)

Status:
RESOLVED INCOMPLETE
Tracking Flags:
Tracking Status
fennec 2.0+ ---

People

(Reporter: dougt, Assigned: mconnor)

References

Details

Calling Weave.Service (which starts up weave) takes up between 300-600ms. This happens processing on the main thread. I am using Fennec on Linux/GTK desktop. The machine is extra fast (SSD, 8 3.x GHz cpus).
tracking-fennec: --- → ?
OS: Mac OS X → All
Hardware: x86 → All
Blocks: 588050
300-600 just for that, or does that include syncing? Is this happening on about:home?
> 300-600 just for that, or does that include syncing? just for that. > Is this happening on about:home? yes. we startup weave on the first DOMContentLoaded message. other interesting factoids: it takes 100-200ms to load and eval all of the random files at the top of service.js in _registerEngines: engines.map(function(name) Weave[name + "Engine"] takes around 150ms
Blocks: 601818
over to mconnor who can reassign as required.
Assignee: nobody → mconnor
tracking-fennec: ? → 2.0+
If you're blocking on this, I presume you have a target for calling it fixed enough to ship?
< 100ms ideally.
Priority: -- → P2
What is going on with this?
More of a meta bug, connor has enough real bugz. marking incomplete.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.