Closed timj closed 7 years ago
@jdswinbank reports that the same commands takes about 38 seconds on lsst-dev01
. The binary install took about 40 minutes rather than 75 minutes.
Ideally I'd like to see this around 15 minutes (the conda install process end to end is 12 minutes for comparison). Over an hour and as my beta tester said, "what's the point, I can use lsstsw".
@RobertLuptonTheGood commented last week that he thinks that the expanded table files should be stored on the server rather than being generated by the client.
I'm planning on working on this today at NRT
R
On 18 May 2017, at 03:38, Tim Jenness notifications@github.com wrote:
@RobertLuptonTheGood commented last week that he thinks that the expanded table files should be stored on the server rather than being generated by the client.
― You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Fix is being tested in #118.
With #118 installed I was able to install w_2017_18
of lsst_distrib
from scratch in less than 8 minutes on my laptop.
Trying a beta of the new binary tarball install system created by @jhoblitt, it ended up taking 75 minutes to install
lsst_distrib
on my Mac. The downloading and untarring were really fast. It seems that the slow down comes from the eups table expansion in https://github.com/RobertLuptonTheGood/eups/blob/master/python/eups/distrib/Repositories.py#L767This runs after each package is installed. With 97 packages and it taking up to 2 minutes per table expansion this really adds up. The above
meas_deblender
snippet takes 75 seconds on my Mac. The initialsetup
calls are about 0.5 second but it ramps up to about 1.5 seconds by the end and there are 78 setup calls.It seems silly that installing binaries should take almost as long as building from source.
@RobertLuptonTheGood, @mjuric do you have any suggestions as to how this could be sped up? Is there any way all the table expansions could run once per
eups distrib install
call with everything setup?