[Python-Dev] Mercurial sluggishness (was: this is what happens if you freeze all the modules required for startup)
Skip Montanaro
skip at pobox.com
Tue Apr 15 17:53:26 CEST 2014
More information about the Python-Dev mailing list
Tue Apr 15 17:53:26 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 10:40 AM, Chris Angelico <rosuav at gmail.com> wrote: > I've no idea whether that's the case or not. All I know is, every time > I need to work with a Mercurial repo it feels a lot slower than doing > similar work on a similar size git repo [1], so any improvement (or > reduction of penalty) will be noticeable. Based on what I saw, I really don't think that startup slowness is in imports of Python stdlib modules, which is all Brett was aiming at. I *can* believe overall import slowness might be a problem, but in that case, Brett's work isn't going to help the Mercurial folks much. Skip
- 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