Maybe spin up an instance on GCE or EC2 and remote into it? If you live anywhere near a data center it should be under 50ms delay. Your time is certainly worth more than whatever the cost of the instance.
Probably. But I always try to build Linux programs natively or in an officially supported environment at the first attempt because I'm not sure what potentially cause problems when I build it in a something unsupported environment. On top of that running the testing framework needed an X11 environment. You know, it sometimes also takes significant times to figure out how to set up in a different environment. I might try EC2 if I became a regular firefox contributor.
> If you live anywhere near a data center it should be under 50ms delay.
Hm, I guess I don't live anywhere near a data center. 1M+ North American city, but lowest ping to any AWS/GCE region is ~130ms.
My RTT from the midwestern US to AWS/Azure/GCP in Germany is less than that. I think your ISP has more blame than your distance to the nearest zone in NA.
Yes, you guys are entirely correct, something looks fishy with my ISP. I'll give them a call them tomorrow morning if it still looks like this.
Edit: Now resolved, pings (barely) over 50ms.
Most likely that latency comes from the link between your place and your ISP.
New York to LA ping time is something like 70ms. Are you going through a proxy?
Re:New Mac Pro Tech Specs
by lonelappde on Thursday September 26, 2019 @10:43PM
(#21087943)
And it's much easier to set up
a build env on a VM than local machine
Woof. I wasn't aware compilation times got that long for people who aren't building a whole OS.
Re:New Mac Pro Tech Specs
by skunkworker on Thursday September 26, 2019 @11:28PM
(#21088143)
Try building Chromium from source. Anandtech uses it as a multithreaded benchmark. The top CPUS can average just under an hour compile time.
I wouldn't try contributing if I were aware of it too lol. Imagine that I did it for Chromium. I was told that it takes about 20GB to build Chromium.
Re:New Mac Pro Tech Specs
by oldmanhorton on Friday September 27, 2019 @12:35AM
(#21088472)
It's usually more, actually. We have seen 100+ GB build directories when building the "all" target and a non-GOMA build easily takes multiple hours on a desktop i7
A browser nowadays is pretty much a whole OS.
Re:New Mac Pro Tech Specs
by TheRealDunkirk on Friday September 27, 2019 @07:28AM
(#21090680)
Hmm... Like when Oracle created their "bare metal" product. There just wasn't much left to add to the database engine to eliminate the need for a general-purpose operating system. I suspect graphics, audio, and pointing input may be significant barriers to doing the same thing here.
Re:New Mac Pro Tech Specs
by tdsamardzhiev on Friday September 27, 2019 @02:16AM
(#21088981)
Well I work in games and building our thing without distributed compilation is inconceivable.
I remember building Mozilla took around 6 hours in my PC back around 2003. Though granted, that was a Pentium II PC with only 128MB of RAM and most of those hours were probably spent with the OS (Linux) swapping stuff :-P.
Are compile farm still relevant in these type of scenario these days?
Yes. As a CI pipeline the Firefox team do run their own compile farm called TryServer [1] and is building a various different versions (possibly all of accepted versions) at a time.
Level 1 contributors (contributors who are acknowledged by one of Mozilla dev) grant access to TryServer.
3 HOURS? Does that say more about your workstation or the project?
I've recently built php + most of the bundled extensions, in a VM (on a 2018 Mac mini) and it's only a couple of minutes at most to build.
Hey it's Firefox, one of the biggest C++ project you can build for now.
A modern browser is a MUCH larger codebase.
Well perhaps if browsers didn't try to cram every feature of a desktop operating system into their own runtime, it wouldn't be?
Seriously. Chrome and Firefox are both guilty of this.
The contribution experience was a nightmare because a full build of Firefox took 3 hrs and running the entire testing framework took 4 hrs, though it turned out that I needed to run only a part of the testing framework. Changing a single line and building it again still took more than 30 minutes.
That was the first moment that I wanted a HEDT in my life. It feels like devs who work with big C++ projects would want a bigger workstation because of the significant build time.