This is just a random thought I posted to http://bugs.darcs.net/issue1293
Perhaps somebody who knows more about computers could run with it? One of the causes of darcs slowness that I personally experience is when my darcs repository is on some kind of network drive, like an NFS share. It's pretty annoying because any time you do something like a darcs add, whatsnew or revert, it sits there for 3-4 seconds reading the pristine cache, just enough time for you to lose your train of thought and (for example) revert the wrong hunk. The workaround is to use darcs on the local hard disk (except e.g. that you lose the automated backups that offered by your institution for the network drive). I'm not sure what the solution to this problem is, or if it affects lots of other folks. But I was thinking that would would be useful would be to make this kind of thing reproducible for benchmarking. So... slow-fs ======= I wish there was some kind of tool that would let me simulate a slow file system (e.g. an NFS share). The idea is that we would do something like (*): mount.slow-fs /pretend/slow/path /actual/location 0.1 And that whenever I tried to read or write from /pretend/slow/path, slow-fs would insert an artificial 0.1 ms (*) delay before actually reading or writing from /actual/location. (*) I don't know what actual mount.foo syntax should look like (**) or whatever units are appropriate -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
