On Wed, May 16, 2012 at 8:15 AM, C. Michael Pilato <[email protected]> wrote: >... > What to do about the commit Ev2 stuff? Perhaps you or Hyrum can help us > understand the scope of the performance cost paid by employing editor shims?
The primary performance cost paid by Ev2 is that the entire edit is queued up during translation, and then replayed upon completion. Some of this intermediate queuing happens in memory, other bits happen on disk, but suffice it to say that for large commits, such intermediate storage may be prohibitive. I don't think it would be a problem for day-to-day work, but for large merges which are common in some organizations I know of, such a performance penalty would be prohibitive. Greg's been hacking around in the shims, and has reduced this cost somewhat, but there is still a O(n) additional resource use cost to consumers of the shim code. -Hyrum -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com/
