[Python-Dev] Issue 11406: adding os.scandir(), a directory iterator returning stat-like info
Antoine Pitrou
solipsis at pitrou.net
Tue May 14 12:34:25 CEST 2013
More information about the Python-Dev mailing list
Tue May 14 12:34:25 CEST 2013
- Previous message: [Python-Dev] Issue 11406: adding os.scandir(), a directory iterator returning stat-like info
- Next message: [Python-Dev] Issue 11406: adding os.scandir(), a directory iterator returning stat-like info
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le Tue, 14 May 2013 22:14:42 +1200, Ben Hoyt <benhoyt at gmail.com> a écrit : > >> It should be no slower when it's all moved to C. > > > > The slowdown is too small to be interesting. The main point is that > > there was no speedup, though. > > True, and thanks for testing. > > I don't think that's a big issue, however. If it's 3-8x faster in the > majority of cases (local disk on all systems, Windows networking), and > no slower in a minority (sshfs), I'm not too sad about that. > > I wonder how sshfs compared to nfs. Ok, with a NFS mount (default options, especially "sync") to the same local VM: First run: os.walk took 17.137s, scandir.walk took 0.625s -- 27.4x as fast Second run: os.walk took 1.535s, scandir.walk took 0.617s -- 2.5x as fast (something fishy with caches?) Regards Antoine.
- Previous message: [Python-Dev] Issue 11406: adding os.scandir(), a directory iterator returning stat-like info
- Next message: [Python-Dev] Issue 11406: adding os.scandir(), a directory iterator returning stat-like info
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list