Can confirm for Ryzen: FWIW, my stock R7 1800x (RAM @2133Mhz for now
:( ) did a Windows debug clobber in 15:32.40 with the default -j16.
(any directory that showed up as read by MsMpEng in Resource Monitor
excluded for Defender)
I'll give it a run through with Defender disabled, and see if
On Fri, Mar 17, 2017 at 7:20 PM, Ben Kelly wrote:
> On Fri, Mar 17, 2017 at 1:36 PM, Ted Mielczarek
> wrote:
>
> With defender
> disabled the best I can get is 18min. This is on one of the new lenovo
> p710 machines with 16 xeon cores.
>
Just to add
On Sun, Mar 26, 2017 at 11:56 PM, Jean-Yves Avenard
wrote:
> Hi.
>
> I have received the new Dell XPS 15 9560 and got very puzzled as to why
> compiling central was so slow on this machine.
> This is comparing against a Gigabyte Aero 14 with a gen 6 intel CPU
> (2.6Ghz
Hi.
I have received the new Dell XPS 15 9560 and got very puzzled as to why
compiling central was so slow on this machine.
This is comparing against a Gigabyte Aero 14 with a gen 6 intel CPU (2.6Ghz
i7-6600HQ) vs Dell's 7th gen (2.8Ghz i7-7700HQ)
On the Aero 14, compiling central takes 24
On Fri, Mar 17, 2017 at 07:13:03PM -0400, Nathan Froyd wrote:
> On Fri, Mar 17, 2017 at 6:31 PM, Mike Hommey wrote:
> > On Fri, Mar 17, 2017 at 03:53:14PM -0400, Boris Zbarsky wrote:
> >> On 3/17/17 3:40 PM, Ted Mielczarek wrote:
> >> > We do try to build js/src pretty early in
On Fri, Mar 17, 2017 at 6:31 PM, Mike Hommey wrote:
> On Fri, Mar 17, 2017 at 03:53:14PM -0400, Boris Zbarsky wrote:
>> On 3/17/17 3:40 PM, Ted Mielczarek wrote:
>> > We do try to build js/src pretty early in the build
>>
>> We do? It's always the last thing I see building
On Fri, Mar 17, 2017 at 03:53:14PM -0400, Boris Zbarsky wrote:
> On 3/17/17 3:40 PM, Ted Mielczarek wrote:
> > We do try to build js/src pretty early in the build
>
> We do? It's always the last thing I see building before we link libxul.
> Seeing the js/src stuff appearing is how I know my
On 03/17/2017 12:40 PM, Ted Mielczarek wrote:
On Fri, Mar 17, 2017, at 03:16 PM, Ben Kelly wrote:
For the 1:38 between Unified_cpp_js_src9.cpp and Interpreter.cpp only
a single cl.exe process is running. I guess thats closer to 8% of the
total build time. Still seems very weird to me.
On 3/17/17 3:40 PM, Ted Mielczarek wrote:
We do try to build js/src pretty early in the build
We do? It's always the last thing I see building before we link libxul.
Seeing the js/src stuff appearing is how I know my build is about done...
-Boris
On Fri, Mar 17, 2017, at 02:43 PM, Ted Mielczarek wrote:
> Similarly, I heard from someone (I can't remember who it was) that said
> they could do a Linux Firefox build in ~8(?) minutes on the same
> hardware. (I will try to track down the source of that number.) That
> gives us a fair lower-bound
On Fri, Mar 17, 2017 at 3:40 PM, Ted Mielczarek wrote:
> Yeah, the JS engine uses a lot more complex C++ features than the rest of
> the code in our tree, so it takes longer to compile. This is also why the
> `FILES_PER_UNIFIED_FILE` setting is lower in js/src than the rest
On Fri, Mar 17, 2017, at 03:16 PM, Ben Kelly wrote:
> On Fri, Mar 17, 2017 at 2:52 PM, Ben Kelly wrote:
>> On Fri, Mar 17, 2017 at 2:43 PM, Ted Mielczarek
>> wrote:
>>
>>
>>
>>
>>
>>> Yeah, I specifically meant "CPU-bound during the compile
On Fri, Mar 17, 2017 at 2:52 PM, Ben Kelly wrote:
> On Fri, Mar 17, 2017 at 2:43 PM, Ted Mielczarek
> wrote:
>
> Yeah, I specifically meant "CPU-bound during the compile tier", where we
>> compile all the C++ code. If you look at the resource usage
On Fri, Mar 17, 2017 at 2:43 PM, Ted Mielczarek wrote:
> > The 14min measurement must have been for a partial build. With defender
> > disabled the best I can get is 18min. This is on one of the new lenovo
> > p710 machines with 16 xeon cores.
>
> Nope, full clobber
On Fri, Mar 17, 2017, at 02:20 PM, Ben Kelly wrote:
> On Fri, Mar 17, 2017 at 1:36 PM, Ted Mielczarek
> wrote:
>
> > Back to the original topic, I recently set up a fresh Windows machine
> > and I followed the same basic steps (enable performance power mode,
> > whitelist a
It looks like there's bug 1188823 [1] for enabling fastlink to improve link
times, but that's in a bad way right now.
FWIW on my ThankPad laptop I have clobber build times in the 35 - 40 minute
range, so even things that seem small for a 16 core desktop are a bigger
win for me.
-e
[1]
On Fri, Mar 17, 2017 at 1:36 PM, Ted Mielczarek wrote:
> Back to the original topic, I recently set up a fresh Windows machine
> and I followed the same basic steps (enable performance power mode,
> whitelist a bunch of stuff in Windows Defender) and my build seemed
>
I filed meta bug 1326328 [1] a few months ago for tracking things we can do
to improve Windows build times. It would be great to file / block existing
bugs against the meta bug to track these issues. There hasn't been much
traction on any of the bugs though, perhaps a good topic for the next
On Fri, Mar 17, 2017, at 01:12 PM, Chris Peterson wrote:
> On 3/17/2017 1:45 AM, Honza Bambas wrote:
> > I have a very similar setup, with even way more exceptions added, but
> > none of them has the desired effect. Unfortunately, the only way to make
> > MsMpEng shut up is to disable run-time
On 3/17/2017 1:45 AM, Honza Bambas wrote:
I have a very similar setup, with even way more exceptions added, but
none of them has the desired effect. Unfortunately, the only way to make
MsMpEng shut up is to disable run-time protection completely for the
time of the build. I think it's a bug in
I have a very similar setup, with even way more exceptions added, but
none of them has the desired effect. Unfortunately, the only way to make
MsMpEng shut up is to disable run-time protection completely for the
time of the build. I think it's a bug in Defender.
On a 20 core system it saves
On 2017-03-17 12:06 AM, Ben Kelly wrote:
On Fri, Mar 17, 2017 at 12:05 AM, Ben Kelly > wrote:
On Thu, Mar 16, 2017 at 11:40 PM, Michael Hoye > wrote:
Depending on your AV, if you
On Fri, Mar 17, 2017 at 12:05 AM, Ben Kelly wrote:
> On Thu, Mar 16, 2017 at 11:40 PM, Michael Hoye wrote:
>
> Depending on your AV, if you don't exempt mozilla-central some of our
>> tests will get quarantined and you won't be able to build at all.
>>
>
>
On Thu, Mar 16, 2017 at 11:40 PM, Michael Hoye wrote:
> Depending on your AV, if you don't exempt mozilla-central some of our
> tests will get quarantined and you won't be able to build at all.
>
I guess I was hoping someone familiar with our build might know the answer.
:-)
Depending on your AV, if you don't exempt mozilla-central some of our tests
will get quarantined and you won't be able to build at all.
- mhoye
On Mar 16, 2017 20:34, "Ben Kelly" wrote:
On Thu, Mar 16, 2017 at 11:26 PM, Ben Kelly wrote:
> -
Try using Sysinternals Process Monitor to see what files MsMpEng.exe is
reading.
On Fri, Mar 17, 2017, at 04:26 PM, Ben Kelly wrote:
> Hi all,
>
> I'm trying to configure my new windows build machine and noticed that
> builds were still somewhat slow. I did:
>
> 1) Put it in high performance
On Thu, Mar 16, 2017 at 11:26 PM, Ben Kelly wrote:
> - mozilla-build install dir
> - visual studio install dir
> - /users/bkelly/appdada/local/temp
> - /users/bkelly (because temp dir was not enough)
>
FWIW, adding all these extra exclusions dropped my build time
Hi all,
I'm trying to configure my new windows build machine and noticed that
builds were still somewhat slow. I did:
1) Put it in high performance power profile
2) Made sure my mozilla-central dir was not being indexed for search
3) Excluded my mozilla-central directory from windows defender
28 matches
Mail list logo