[Python-Dev] Issue 11406: adding os.scandir(), a directory iterator returning stat-like info
Antoine Pitrou
solipsis at pitrou.net
Tue May 14 11:05:25 CEST 2013
More information about the Python-Dev mailing list
Tue May 14 11:05: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 20:54:50 +1200, Ben Hoyt <benhoyt at gmail.com> a écrit : > >> If anyone can run benchmark.py on Linux / NFS or similar, that'd be > >> great. You'll probably have to lower DEPTH/NUM_DIRS/NUM_FILES first > >> and then move the "benchtree" to the network file system to run it > >> against that. > > > > Why does your benchmark create such large files? It doesn't make > > sense. > > Yeah, I was just thinking about that last night, and I should probably > change that. Originally I did it because I thought it might affect the > speed of directory walking, so I was trying to make some of the files > large to be more "real world". I've just tested it, and in practice > file system doesn't make much difference, so I've fixed that now: Thanks. I had bumped the number of files, thinking it would make things more interesting, and it filled my disk. 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