Announcing MozillaBuild 3.1.1 Release
rvandermeulen at mozilla.com
Wed Nov 29 01:42:36 UTC 2017
I was seeing regressions on the order of magnitude scale for basic
operations like updating between revisions. i.e. what should have taken
10-15sec taking closer to 5min. And this is on an NVMe SSD. So I guess as
usual, YMMV depending specific work flows. If you haven't noticed any major
issues, then it's probably not a huge deal for now.
On Tue, Nov 28, 2017 at 8:03 PM, Xidorn Quan <me at upsuper.org> wrote:
> On Wed, Nov 29, 2017, at 10:55 AM, Ryan VanderMeulen wrote:
> * The fsmonitor extension was re-disabled due to significant performance
> regressions for some common operations caused by watchman excessively
> polling the filesystem.
> If you're already using version 3.1 without issue, you probably don't need
> to pick up this release. You may want to consider disabling fsmonitor in
> the mean time, however. You can do that by making the change below to
> It isn't clear to me what performance issue it has.
> From the bug, I can see the issue gps raised on GitHub:
> So my question would be, does it affect building Firefox in subdirectory
> of working directory? If it does, then it sounds very serious and people
> should probably disable it. If it doesn't, maybe it isn't a too big deal,
> since I don't think most developers want to create tons of files frequently.
> - Xidorn
> firefox-dev mailing list
> firefox-dev at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the firefox-dev