810148 - Repack/Reorder extensions when they are released on amo

Status: RESOLVED INACTIVE

(Toolkit :: Add-ons Manager, defect)

Description

[(dormant account)]

This sort of optimization can significantly cut down on amount of IO, memory usage, etc. We do this with omni.ja can reuse the same infrastructure.

Comment 1

[Dave Townsend [:mossop]]

Can you explain more about what this involves?

Comment 2

[(dormant account)]

(In reply to Dave Townsend (:Mossop) from comment #1)
> Can you explain more about what this involves?

Starting the browser with the extension, collection the access log and then repacking the extension based on order of files accessed

Comment 3

[Dave Townsend [:mossop]]

So something AMO should do or something we should do everytime an extension is installed in Firefox?

Comment 4

[(dormant account)]

(In reply to Dave Townsend (:Mossop) from comment #3)
> So something AMO should do or something we should do everytime an extension
> is installed in Firefox?

Either.

Comment 5

[(not currently active) Ted Mielczarek]

I think this is probably a big scope of work for AMO to implement. I'm fairly certain AMO doesn't have any ability to run Firefox on arbitrary addons at the moment.

Comment 6

[(dormant account)]

(In reply to Ted Mielczarek [:ted.mielczarek] from comment #5)
> I think this is probably a big scope of work for AMO to implement. I'm
> fairly certain AMO doesn't have any ability to run Firefox on arbitrary
> addons at the moment.

Was AMO running Ts for a large number of addons?

Comment 7

[(not currently active) Ted Mielczarek]

That was pretty standalone from AMO:
https://developer.mozilla.org/en-US/docs/Performance/Measuring_add-on_startup_performance

I don't think we're actually running those anymore, but AFAIK we ran them on a separate pool of slaves and just reported the data to AMO.

Comment 8

[Blair McBride [:Unfocused] (UNAVAILABLE)]

Indeed, that hasn't been hooked up for some time. I've been pushing a plan to get that infrastructure eventually working again, with different goals in mind - but don't expect that to happen any time soon.

In general, we found that running add-ons in an automated environment like that wasn't representative enough of real-world usage. But it might be good enough for this - since the files loaded on startup should usually be the same.

But, re-ordering on the AMO-side won't be much use if we want to look at a single omni.jar for all installed add-ons.

Comment 9

[BMO Automation]

Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.