[Python-Dev] Mercurial sluggishness (was: this is what happens if you freeze all the modules required for startup)
Daniel Holth
dholth at gmail.com
Tue Apr 15 19:32:43 CEST 2014
More information about the Python-Dev mailing list
Tue Apr 15 19:32:43 CEST 2014
- Previous message: [Python-Dev] Mercurial sluggishness (was: this is what happens if you freeze all the modules required for startup)
- Next message: [Python-Dev] Mercurial sluggishness (was: this is what happens if you freeze all the modules required for startup)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Apr 15, 2014 at 1:29 PM, Antoine Pitrou <solipsis at pitrou.net> wrote: > Le 15/04/2014 19:09, Daniel Holth a écrit : > >> In case you were wondering, I'm using Ubuntu's "2.7.5+" and "3.3.2+". >> >> My feeling has long been that the speed of getting at the "--help" >> option or any initial user feedback from Mercurial or git is a big >> driver in perceived speed as opposed to how long the entire operation >> might take. But for me any initial speed improvements from git are >> fully offset by the feeling of irritation afterwards. /troll >> >> For me Python's startup time (warm) takes about 1/4 of the hg startup >> time in the worst case. I expect to both notice and appreciate any >> speedups and encourage all optimizers to optimize. > > > Well, if we optimize 11% out of that 1/4, I don't expect you to notice the > speedup at all ;-) > > > Regards > > Antoine. No one expects the Spanish Inquisition.
- Previous message: [Python-Dev] Mercurial sluggishness (was: this is what happens if you freeze all the modules required for startup)
- Next message: [Python-Dev] Mercurial sluggishness (was: this is what happens if you freeze all the modules required for startup)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list