On Tue, Mar 23, 2010 at 8:28 AM, Stefan Sperling <s...@elego.de> wrote:
> In most setups I've seen the server hardware is much beefier than > the client hardware, so unless we do things that scale really badly > (say more than O(n^2)) I don't see a problem. Think of a hosting site like sf.net with thousands of SVN repos being hit by many thousands of users. How many of these operations do you think the Apache server could manage before it ran out of RAM? I am not saying we cannot ask the server to do more, but if you start having it hang on to a list of paths, as you suggest in the rename case, I do not see how it will not run into scenarios where that does not involve significant amounts of memory usage. -- Thanks Mark Phippard http://markphip.blogspot.com/
