Is there any reason why we shouldn't modify buildx.sh for the X11 rdp server in /xorg to use multiple cores?
The scarygliders utility currently does a blind sed that replaces all make instances with "make -j" -- That appears to have worked with older versions of the software, but it doesn't work now. I just ran a test by modifying the command in "make_it" by changing the cores to 8, and it appears to have shaved about 5 minutes off the build time, the reason this wasn't faster is the limiting factor in the build was disk access, all 8 cores were in use, but rarely did they get above 50% utilization each. In fact, even with using a single core, it rarely went to 100% utilization. All of this could be muted by the fact that I'm running Ubuntu in a virtual machine (Hyper-V). The first time I built it took about 25 minutes on a Core i7 (including the downloading of files). The second time I built with 8 cores it took 15 minutes, but I'm giving 5 minutes to the time to download files, thus about a 5 minute improvement I'm thinking I will modify buildx.sh to take a parameter: sudo ./buildx.sh -c X where X is the number of cores to use. This would be helpful for the scarygliders utility, too. Thoughts? -- View this message in context: http://xrdp-devel.766250.n3.nabble.com/XRDP-devel-Optimizing-buildx-sh-to-use-multiple-cores-tp4024933.html Sent from the XRDP Devel mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 _______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-devel
