On Tuesday, 24 November 2015 17:16:29 UTC, Volker Braun wrote: > > I'm pretty sure its IO bound, so parallelization won't help. You have to > run it only once anyways... >
well, I see (running top) Python process taking somewhere between 70 and 95% of one CPU almost all the time while I run the installation script. Unless this does include I/O, it seems to indicate that parallelisation would actually help. (It might be different on a "real" disk - I have an SSD). By the way, surprisingly (to me at least) it was even possible to do 'make test', and have all, save for couple of timeouts, pass. Although first thing that happened was installation of gcc spoke from source, followed by rebuilding of (almost?) all spkg's. It is what one would expect? Perhaps it's good to try to understand what can be shipped in a binary so that this rebuilding is not needed... Dima > On Tuesday, November 24, 2015 at 3:27:49 PM UTC+1, Dima Pasechnik wrote: >> >> great, I can confirm that this gives seemingly working Sage in such a >> settings (SIP on, i.e. as 99% of users will have) >> on a Core2Duo machine running OSX 10.11.1. >> >> install.py a bit slow though... perhaps it should be run in parallel. >> >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
