Closed Bug 443600 Opened 11 years ago Closed 11 years ago

Optimize HgLocalePoller and pushlog communication


(Developer Services :: Mercurial:, defect, P3)



(Not tracked)



(Reporter: Pike, Unassigned)


The HgLocalePoller in currently hits each l10n repository per se.

So we're talking about opening 50-100+ connections between the buildmaster and the hg server. Doing so in serial isn't great, and doing so in parallel isn't really either?

If we want to kick off nightly builds as triggered builds from en-US nightlies, which we do, then we'll likely even open these connections from our most precious master. Frank. N. Furter comes to my mind right now, excuse the distraction.

I would imagine that we could optimize this by extending the pushlog hook on and to add an additional commit hook to all l10n repositories, adding themselves to a single db with an additional column for the locale.

Ted, Benjamin, one thing I don't know is if we can actually extend hgweb at a parent dir of repositories. Something like, picking up the style stuff from #developers.

I'll need you guys to tell me if that makes any sense at all, too.

And probably joduinn to say if it has to make sense in one way or another.
Unclear what we are supposed to do here. Can we try getting l10n builds started first and then if this is really a problem, we can reopen this bug?
Component: Release Engineering → Release Engineering: Future
Priority: -- → P3
I have a buildbot running pounding those feeds and it responds quickly, so it doesn't seem to care too much.

Resolving WORKSFORME, in the right component though.
Closed: 11 years ago
Component: Release Engineering: Future → Hg: Customizations
Resolution: --- → WORKSFORME
Product: → Release Engineering
Product: Release Engineering → Developer Services
You need to log in before you can comment on or make changes to this bug.