@cmuratori That's what @nothings uses, but I want an off-site repo. I used an svn repo host for a while but they're a little sketch.
-
-
Replying to @HookTM
@GrumpyHook@nothings Sadly, it also has the drawback of being _way too slow_ on Linux, because their inode enumeration fucking blows.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@GrumpyHook@nothings Last time I asked, you were running this *on a NTFS partition* under Linux.2 replies 0 retweets 1 like -
Replying to @rygorous
@rygorous@GrumpyHook@nothings I think you are misremembering. This is on ext3 and ext4 partitions.2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@GrumpyHook@nothings Also, did you try ftw(3) or fts(3)? No offense, but I'm not sure I trust your traversal code. :)1 reply 0 retweets 1 like -
Replying to @rygorous
@rygorous@GrumpyHook@nothings I timed readdir, readdirstat, ftw, and glob.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@rygorous@GrumpyHook@nothings You can make it _very_ fast by never asking for the timestamp. But as far as I've found...1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@rygorous@GrumpyHook@nothings ...anything that gets the timestamps is hella slow.3 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@rygorous@GrumpyHook If ext3/4 update dir write timestamp when child file is altered, you could do "cache & stat the dirs" trick2 replies 0 retweets 0 likes -
Replying to @nothings
@nothings@rygorous@GrumpyHook I didn't bother going further because I am working on the cmirror replacement anyway, and it's almost done.1 reply 0 retweets 0 likes
@cmuratori @nothings @rygorous @GrumpyHook So dir iteration will be a non-issue at that point.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.