Hi all, Thank you for your replies. This post is to clarify and talk about the issues and questions raised.
Time taken by patch index: I have primarily tested patch index on darcs screened repository. The time it takes to build patch index varies based upon the contents in the disk cache. For example, when you build patch index just after get, it takes around 6sec. If you clear the disk cache it takes 1min. This is typical of any darcs command. The commands tend to be slower at the start of a session. They speed up after a few runs. Patch index will also cause a lag when the repository state changes by record/pull/apply etc. However, in practice it seems to be negiligible. I have measured the time taken by changes<https://docs.google.com/spreadsheet/ccc?key=0AtdxF5AhJcuwdGdrT2lLMGZXbktZblFxWmhxNkxXRVE#gid=0>and annotate<https://docs.google.com/spreadsheet/ccc?key=0AtdxF5AhJcuwdHFlMm0xd1poeTROYW1KN0ZGR2U0enc#gid=0>using patch index and without patch index, in both cold(cleared disk cache) and hot states(disk cache has relavant files in memory). On average, patch index reduced 92% of time taken in hot changes, 78% of time taken in cold changes, 94% of time taken in hot annotate, 86% of time taken in cold annotate. Patch index with read only repositories: patch index will work with read only repositories. However, before changing the repository to read only, it has to be ensured that patch index is upto date.(use show patch-index-status) This will usually be the case, unless the last changes was made by an old darcs. Feedback when building patch index: darcs will print a message about building patch index when patch index darcs is run on existing repositoreis. In other cases, patch index is updated/used/created silently. Rename --no-patch-index to --disable-patch-index : I have implemented this suggestion. Ctrl-C at get: I have added support for this. If you use ctrl-c to interupt get, patch index will be disabled. ctrl-c at creation on an old repo: I will add support for this. ctrl-c at update of patch index: I do not see the need for this, as the time for update is quite small. incremental creation of patch index: while the time taken to create patch index can be annoying (1min at worst on darcs repository), it is not large enough to warrant this, I think. Disable automatic patch index creation on old repositories: One of my mentors(Benedikt) suggested that we could add a universal flag no-automatic-patch-index. This is to address a case, where the user does not want to automatically create patch index on existing repositories. The user could then add ALL no-automatic-patch-index to the global defaults file. Do users feel the need for such a feature? Should the flag disable patch index at repository creation too? My latest code is at: http://darcsden.com/bsrkaditya/darcs-patch-index Aditya
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
