[Numpy-discussion] "import numpy" is slow
Thu Jul 31 07:31:49 CDT 2008
I've been reading this discussion with interest.
I would just to highlight an alternate use of numpy to interactive use. We
have a cluster of machines which process tasks on an individual basis where
a master tasks may spawn 600 slave tasks to be processed. These tasks are
spread across the cluster and processed as scripts in a individual python
thread. Although reducing the process time by 300 seconds for the master
task is only about a 1.5% speedup (total time can be i excess of 24000s). We
process large number of these tasks in any given year and every little
2008/7/31 Stéfan van der Walt <firstname.lastname@example.org>
> 2008/7/31 Andrew Dalke <email@example.com>:
> > The user base for numpy might be .. 10,000 people? 100,000 people?
> > Let's go with the latter, and assume that with command-line scripts,
> > CGI scripts, and the other programs that people write in order to
> > help do research means that numpy is started on average 10 times a day.
> > 100,000 people * 10 times / day * 0.1 seconds per startup
> > = almost 28 people-hours spent each day waiting for numpy to start.
> I don't buy that argument. No single person is agile enough to do
> anything useful in the half a second or so it takes to start up NumPy.
> No one is *waiting* for NumPy to start. Just by answering this
> e-mail I could have (and maybe should have) started NumPy three
> hundred and sixty times.
> I don't want to argue about this, though. Write the patches, file a
> ticket, and hopefully someone will deem them important enough to apply
> Numpy-discussion mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Numpy-discussion