Re: [sage-devel] Re: profiling Sage startup

2011-08-17 Thread Julian Rüth
* William Stein [2011-08-12 11:30:21 -0700]: > On Fri, Aug 12, 2011 at 10:05 AM, Julian Rüth wrote: > > I'm not sure if this discussion has been picked up in a different thread > > since February but the problem with zipimport seems to be that it can't load > > .so files. Since we have plenty of

Re: [sage-devel] Re: profiling Sage startup

2011-08-12 Thread William Stein
On Fri, Aug 12, 2011 at 10:05 AM, Julian Rüth wrote: > I'm not sure if this discussion has been picked up in a different thread > since February but the problem with zipimport seems to be that it can't load > .so files. Since we have plenty of them, just loading the .py files from a > zip file and

Re: [sage-devel] Re: profiling Sage startup

2011-03-03 Thread Harald Schilly
On Wednesday, February 23, 2011 10:56:10 PM UTC+1, robertwb wrote: > > And this is with the directory presumably in the FS cache. ... just because I read this, you can flush the disk cache via: sudo sh -c "sync && echo 3 > /proc/sys/vm/drop_caches" H -- To post to this group, send an email

Re: [sage-devel] Re: profiling Sage startup

2011-03-01 Thread Robert Bradshaw
On Tue, Mar 1, 2011 at 10:07 AM, David Kirkby wrote: > On 1 March 2011 15:38, daly wrote: >> Sage could follow the same technique used by Gimp. >> Gimp loads a huge number of files at startup and can >> take over a minute to start on small systems. They >> have a startup splash screen that shows

Re: [sage-devel] Re: profiling Sage startup

2011-03-01 Thread Robert Bradshaw
On Tue, Mar 1, 2011 at 4:56 AM, luisfe wrote: > On Mar 1, 1:32 pm, "Johan S. R. Nielsen" > wrote: >> On Mar 1, 10:13 am, Robert Bradshaw >> wrote: >> >> Nice! I weren't aware of this module. When you get a good idea, >> there's a good chance that someone else thought of it before ;-) I >> like t

Re: [sage-devel] Re: profiling Sage startup

2011-03-01 Thread Robert Bradshaw
On Tue, Mar 1, 2011 at 4:32 AM, Johan S. R. Nielsen wrote: > On Mar 1, 10:13 am, Robert Bradshaw > wrote: >> On Tue, Mar 1, 2011 at 12:48 AM, Johan S. R. Nielsen >> >> >> >> wrote: >> > On Feb 23, 11:03 pm, Jason Grout wrote: >> >> On 2/23/11 3:56 PM, Robert Bradshaw wrote: >> >> >> > On Wed, F

Re: [sage-devel] Re: profiling Sage startup

2011-03-01 Thread David Kirkby
On 1 March 2011 15:38, daly wrote: > Sage could follow the same technique used by Gimp. > Gimp loads a huge number of files at startup and can > take over a minute to start on small systems. They > have a startup splash screen that shows the files > which are being loaded. That way the user sees p

Re: [sage-devel] Re: profiling Sage startup

2011-03-01 Thread daly
Sage could follow the same technique used by Gimp. Gimp loads a huge number of files at startup and can take over a minute to start on small systems. They have a startup splash screen that shows the files which are being loaded. That way the user sees progress during startup. -- To post to this g

Re: [sage-devel] Re: profiling Sage startup

2011-03-01 Thread Robert Bradshaw
On Tue, Mar 1, 2011 at 12:48 AM, Johan S. R. Nielsen wrote: > On Feb 23, 11:03 pm, Jason Grout wrote: >> On 2/23/11 3:56 PM, Robert Bradshaw wrote: >> >> >> >> > On Wed, Feb 23, 2011 at 1:47 PM, Jason Grout >> >  wrote: >> >> On 2/23/11 3:06 PM, Robert Bradshaw wrote: >> >> >>> On Wed, Feb 23, 2

Re: [sage-devel] Re: profiling Sage startup

2011-02-23 Thread Robert Bradshaw
On Wed, Feb 23, 2011 at 1:47 PM, Jason Grout wrote: > On 2/23/11 3:06 PM, Robert Bradshaw wrote: >> >> On Wed, Feb 23, 2011 at 11:34 AM, William Stein  wrote: >>> >>> On Wed, Feb 23, 2011 at 10:57 AM, Jason Grout >>>  wrote: On 2/23/11 12:28 PM, William Stein wrote: > > At lunch

Re: [sage-devel] Re: profiling Sage startup

2011-02-23 Thread Robert Bradshaw
On Wed, Feb 23, 2011 at 11:34 AM, William Stein wrote: > On Wed, Feb 23, 2011 at 10:57 AM, Jason Grout > wrote: >> On 2/23/11 12:28 PM, William Stein wrote: >>> >>> At lunch yesterday Robert Bradshaw made the interesting suggestion to >>> read the docs for importlib >>> (http://docs.python.org/de

Re: [sage-devel] Re: profiling Sage startup

2011-02-23 Thread William Stein
On Wed, Feb 23, 2011 at 10:57 AM, Jason Grout wrote: > On 2/23/11 12:28 PM, William Stein wrote: >> >> At lunch yesterday Robert Bradshaw made the interesting suggestion to >> read the docs for importlib >> (http://docs.python.org/dev/library/importlib.html) and write a >> customized import hook,

Re: [sage-devel] Re: profiling Sage startup

2011-02-23 Thread William Stein
On Wed, Feb 23, 2011 at 7:09 AM, Volker Braun wrote: > Its true that there are lots of failed attempts to get files, which is > normal for any system where you have a multiple directories which can > contain any given file: > > [vbraun@volker-desktop ~]$ echo quit | strace -f sage |& grep ENOENT |

Re: [sage-devel] Re: profiling Sage startup

2011-02-23 Thread Robert Bradshaw
On Wed, Feb 23, 2011 at 4:43 AM, Volker Braun wrote: > I take it that the slow thing is reading ~2000 sage library files from a > harddisk into the filesystem cache. I'm using SSDs and Sage starts > consistently within about 1 second. There is "sage -startuptime" to profile. > The way I see it, th