Hi, I am a student participating in Google Summer of Code for darcs. I work on an optimization called patch index. I would like to get some feedback on my project.
Patch index improves the speed of changes and annotate commands by quickly identifying the patches that modified a given file. This optimization is especially useful for large repositories. The public repository is at: http://den.darcs.net/Aditya/darcs-patch-index Patch index will be automatically created upon get or init. If you run changes/annotate/record/.. using patch index darcs on an existing repository, patch index will be created automatically. Alternatively, run optimize --patch-index to exclusively create patch index. You can disable patch index using optimize --no-patch-index, and enable it back with optimize --patch-index. If you wish to disable patch index at creation, pass --no-patch-index. A lazy get will implicitly disable patch index, as you require to have all patches to create a patch index. I request users to try patch index darcs, and give feedback on potential ui changes, bugs etc One of the concerns I already have is automatic creation of patch index on existing repositories. The time it takes to create patch index increases dramatically based on buffer cache<http://oss.sgi.com/LDP/LDP/sag/buffer-cache.html>. Creating a patch index just after get takes 6 sec, whereas it takes 1min after cleaning the cache(This is for darcs development repo). This suggests that a user could experience a potentially large delay on changes/record/.. . BSRK Aditya
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
