[chromium-dev] Re: Any way to compile webkit faster
Mohamed, if you wish i can share with you the tricks i do on my machine they make the difference of even building chrome.exe from 10 mins to less than 1 (after a small source code change) all this on my very very slow machine i wrote a small exe program which parses the .vsprops and ..vcproj so regardless of which props the project uses you get all the benefits you get /MP you get incremental linking (no Comdat folding and no opt:ref) no warning from the linker for /NOWIN98 (or however it is called) there are some catches as you will get more tree conflicts when you sync, but you can always delete your .vcproj,.vsprops file and sync --force the speed gains are truly amazing (at least 10x when you modify source code, because of the incremental link) there are other ugly parts to it but if you want it, i can send you the exe or the source code so you can use it on your machine this is all tested to never produce any problem (so far) on VS2008 SP1 --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Any way to compile webkit faster
Do you think it will also work for Visual Studio 2005 and Windows Vista? ☆PhistucK On Thu, Jun 11, 2009 at 12:39, nakro yoav.zilberb...@gmail.com wrote: Mohamed, if you wish i can share with you the tricks i do on my machine they make the difference of even building chrome.exe from 10 mins to less than 1 (after a small source code change) all this on my very very slow machine i wrote a small exe program which parses the .vsprops and ..vcproj so regardless of which props the project uses you get all the benefits you get /MP you get incremental linking (no Comdat folding and no opt:ref) no warning from the linker for /NOWIN98 (or however it is called) there are some catches as you will get more tree conflicts when you sync, but you can always delete your .vcproj,.vsprops file and sync --force the speed gains are truly amazing (at least 10x when you modify source code, because of the incremental link) there are other ugly parts to it but if you want it, i can send you the exe or the source code so you can use it on your machine this is all tested to never produce any problem (so far) on VS2008 SP1 --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Any way to compile webkit faster
By last gyp Sverrir, do you mean the modules in chrome.sln switching over, or the ones in webkit?There was one generated set of targets in webkit.gyp, that we ended up adding a makefile emission option for. It was just too slow with rules (all the overhead of crossing over into cygwin per file). There are some rules in chrome.gyp that might have similar properties and would benefit from turning on the makefile option for those rules. -BradN On Thu, Jun 11, 2009 at 7:40 AM, Sverrir Á. Berg sver...@chromium.orgwrote: Just wanted to echo Mohamed's findings. My build has been very slow the past two weeks. I'm using VS2008 and I have not used /MP recently. I have a top of the line machine (xw6600 Quad Core 8G mem, Intel SSD) and building chrome.exe after a sync/clean takes approx 40 minutes. I think this started approximately around the last gyp change... Sverrir On Thu, Jun 11, 2009 at 6:03 AM, nakro yoav.zilberb...@gmail.com wrote: most of it will, but i never tried it however, i saw here in this forum ppl complaining that /MP on 2005 creates corrupted .PDB (the debug info) files so i don't know, but the incremental linking should work if you wish you can PM me and i will send you whatever you want (even the tool i wrote to make Cl.exe run in IDLE_PRIORITY_CLASS so i don't die while code compiles) but i just warn you that these things are not supported by chrome so do it at your own risk --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Any way to compile webkit faster
Most of the losses were regained for me about 2 weeks ago... I am somewhat surprised to hear that you're still getting bad performance. Are you re-running gyp after you apply the /MP patch? -Ben On Wed, Jun 10, 2009 at 7:19 PM, Mohamed Mansourm0.interact...@gmail.com wrote: Hello, Ever since webkit converted to GYP, the time, chromium compilation went from 25 minutes to literally 1 hour and 20+ minutes. (that is by just doing a gclient sync every day) Are there any suggestions on how to make it quicker? (yes I followed the dev documentation) and I have applied the following /MP tags, http://codereview.chromium.org/115603 But I don't understand why my CPU is set to 20-25% active for webkit compilation and chromium uses 100%. It is really getting annoying for any gclient sync, I have to wait roughly 1hr + for me to use the code again. Out of my two to three hours a day working on chromium (about), two thirds of it goes on compiling. I would rather be productive and land couple of patches. Any suggestions is highly appreciated. -- Mohamed Mansour --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Any way to compile webkit faster
What does your NUMBER_OF_PROCESSORS environment variable have set?What happens if you set it explicitly to 4? -BradN On Wed, Jun 10, 2009 at 7:43 PM, Mohamed Mansour m0.interact...@gmail.comwrote: +dev -- Forwarded message -- From: Mohamed Mansour m0.interact...@gmail.com Date: Wed, Jun 10, 2009 at 10:43 PM Subject: Re: [chromium-dev] Any way to compile webkit faster To: Ben Goodger (Google) b...@chromium.org Yes, I do this all the time after every gclient sync --force, gclient runhooks --force Does your webkit use all 4 CPU's while compiling? Mine just uses 1 CPU at 100% the others nothing. While chromium just uses all 4 at 100%. -- Mohamed Mansour On Wed, Jun 10, 2009 at 10:38 PM, Ben Goodger (Google) b...@chromium.orgwrote: Most of the losses were regained for me about 2 weeks ago... I am somewhat surprised to hear that you're still getting bad performance. Are you re-running gyp after you apply the /MP patch? -Ben On Wed, Jun 10, 2009 at 7:19 PM, Mohamed Mansourm0.interact...@gmail.com wrote: Hello, Ever since webkit converted to GYP, the time, chromium compilation went from 25 minutes to literally 1 hour and 20+ minutes. (that is by just doing a gclient sync every day) Are there any suggestions on how to make it quicker? (yes I followed the dev documentation) and I have applied the following /MP tags, http://codereview.chromium.org/115603 But I don't understand why my CPU is set to 20-25% active for webkit compilation and chromium uses 100%. It is really getting annoying for any gclient sync, I have to wait roughly 1hr + for me to use the code again. Out of my two to three hours a day working on chromium (about), two thirds of it goes on compiling. I would rather be productive and land couple of patches. Any suggestions is highly appreciated. -- Mohamed Mansour --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Any way to compile webkit faster
FWIW - There also is a setting in Developer Studio that specifies how many projects Visual Studio can build simultaneously. Maybe it is unrelated but I wonder if that is set to 1 or something for you? Tools \ Options \ Projects and Solutions \ Build and Run. I have a Quad Core and have this set to 4. PS. Why don't you just use gclient sync and build solution/F5? I never use the --force param when sync'ing and haven't needed to use runhooks yet. Yet I have no problems with my build... On Wed, Jun 10, 2009 at 19:43, Mohamed Mansour m0.interact...@gmail.comwrote: +dev -- Forwarded message -- From: Mohamed Mansour m0.interact...@gmail.com Date: Wed, Jun 10, 2009 at 10:43 PM Subject: Re: [chromium-dev] Any way to compile webkit faster To: Ben Goodger (Google) b...@chromium.org Yes, I do this all the time after every gclient sync --force, gclient runhooks --force Does your webkit use all 4 CPU's while compiling? Mine just uses 1 CPU at 100% the others nothing. While chromium just uses all 4 at 100%. -- Mohamed Mansour On Wed, Jun 10, 2009 at 10:38 PM, Ben Goodger (Google) b...@chromium.orgwrote: Most of the losses were regained for me about 2 weeks ago... I am somewhat surprised to hear that you're still getting bad performance. Are you re-running gyp after you apply the /MP patch? -Ben On Wed, Jun 10, 2009 at 7:19 PM, Mohamed Mansourm0.interact...@gmail.com wrote: Hello, Ever since webkit converted to GYP, the time, chromium compilation went from 25 minutes to literally 1 hour and 20+ minutes. (that is by just doing a gclient sync every day) Are there any suggestions on how to make it quicker? (yes I followed the dev documentation) and I have applied the following /MP tags, http://codereview.chromium.org/115603 But I don't understand why my CPU is set to 20-25% active for webkit compilation and chromium uses 100%. It is really getting annoying for any gclient sync, I have to wait roughly 1hr + for me to use the code again. Out of my two to three hours a day working on chromium (about), two thirds of it goes on compiling. I would rather be productive and land couple of patches. Any suggestions is highly appreciated. -- Mohamed Mansour --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
