On 8/22/13 7:04 PM, Mark Hammond wrote:
On 21/08/2013 5:36 AM, Gregory Szorc wrote:
...
Finally, this is just a friendly reminder that if you build
mozilla-central and you don't have a machine with at least 4 *physical*
cores, 16 GB RAM, and an SSD, you should upgrade your hardware.
FTR, my
On 23/08/2013 04:04, Mark Hammond wrote:
FTR, my Windows machine has 16GB of ram, 4 physical cores, and both SS
and spinning disks. A debug clobber build takes 34 minutes on the
spinning disk and 31 on the SSD - so the wins of an SSD on my box aren't
quite as large as I was expecting (I suspect
On 2013-08-22 10:04 PM, Mark Hammond wrote:
On 21/08/2013 5:36 AM, Gregory Szorc wrote:
...
Finally, this is just a friendly reminder that if you build
mozilla-central and you don't have a machine with at least 4 *physical*
cores, 16 GB RAM, and an SSD, you should upgrade your hardware.
FTR,
On 8/23/13 1:16 PM, Ehsan Akhgari wrote:
Finally, this is just a friendly reminder that if you build
mozilla-central and you don't have a machine with at least 4 *physical*
cores, 16 GB RAM, and an SSD, you should upgrade your hardware.
FTR, my Windows machine has 16GB of ram, 4 physical
On 21/08/2013 5:36 AM, Gregory Szorc wrote:
...
Finally, this is just a friendly reminder that if you build
mozilla-central and you don't have a machine with at least 4 *physical*
cores, 16 GB RAM, and an SSD, you should upgrade your hardware.
FTR, my Windows machine has 16GB of ram, 4
Now in inbound, |mach build| will record *system* resource usage during
builds. You can later view the resource usage by running |mach
resource-usage| (mach will tell you at the end of the build if you can
run this).
The goal of this feature is to help people diagnose why builds are slow
and
6 matches
Mail list logo