On Thu, Jul 03, 2014 at 05:38:42AM -0700, Volker Braun wrote:
> On Thursday, July 3, 2014 6:59:45 AM UTC-4, Nicolas M. Thiéry wrote:
>
> Compiling in place means saving 15s of `sage -b` each time I just
> modify Python code
>
> Hmm can you describe your hardware and filesystem? After editing a
> Python file, "echo quit | sage -br" takes me 4.8 seconds. Just running
> + quitting (without -b) takes 1.4 seconds.
> Of the actual build time, 2.4 seconds is spent in cythonize
> checking that no dependency changed. Copying Python files
> accounts for maybe 10% of the dev cycle time. Could probably be
> done in parallel with cythonize, in which case it is basically
> for free.
Strange! I am jealous :-)
> time sage -b
sage -b 12,17s user 1,62s system 99% cpu 13,845 total
> time "echo quit | sage -br"
sage -br 15,18s user 2,01s system 95% cpu 18,021 total
My laptop is 1.5 years old, with SSE disk, Intel I7 @2.60 MHz 8 cores,
8Go of RAM; it should still be in the rather high end. Ubuntu, ext4, a
priori nothing specific configured (except for the make -j8 by
default). I'd be delighted to learn any trick to configure it better!
Agreed, any time we can save in `sage -b` is more than welcome.
That being said, in place building would still be compelling:
- less confusion with tools like debugger and editor
- live reloading of python modules
- ...
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" <[email protected]>
http://Nicolas.Thiery.name/
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
