web commit by http://id.inelegant.org/: Comment on potential scaling issue.

2007-03-16 12:28:52 +00:00 · 2007-03-16 12:28:52 +00:00 · 50408be042
parent 4e697ad425
commit 50408be042
1 changed files with 1 additions and 0 deletions
--- a/doc/subversion/discussion.mdwn
+++ b/doc/subversion/discussion.mdwn
@ -0,0 +1 @@
+If the user interrupts the page loading during the running of `svn commit`, the repository will be left in an inconsistent state. The probability of this happening increases with the size of the repository and the number of plugins installed, because these both affect how long the post-commit hook takes to run. (The core issue, I guess, is that we're abusing the concept of a "working copy" by giving everybody the same one). Here are the main solutions that I can see: (1) CGI queues commits so that a single process can act upon them sequentially, or (2) optionally divorce the `ikiwiki --refresh` from the `svn commit` so that commits happen faster. -- [[Ben]]
				`@ -0,0 +1 @@`
				If the user interrupts the page loading during the running of `svn commit`, the repository will be left in an inconsistent state. The probability of this happening increases with the size of the repository and the number of plugins installed, because these both affect how long the post-commit hook takes to run. (The core issue, I guess, is that we're abusing the concept of a "working copy" by giving everybody the same one). Here are the main solutions that I can see: (1) CGI queues commits so that a single process can act upon them sequentially, or (2) optionally divorce the `ikiwiki --refresh` from the `svn commit` so that commits happen faster. -- [[Ben]]