Rüdiger: On Mon, Oct 7, 2019 at 3:51 PM Ruediger Pluem <rpl...@apache.org> wrote:
> On 10/07/2019 08:40 PM, Branko Čibej wrote: > > On Mon, 7 Oct 2019, 19:47 Doug Robinson, <doug.robin...@wandisco.com > <mailto:doug.robin...@wandisco.com>> wrote: > > > > Folks: > > > > I spoke with this user late last week. They stated that they can > only get approximately 400 parallel SVN operations > > before the "system time" consumes all available CPU for an 8-core > machine. Adding more cores won't help because of > > the nature of spin locks (it makes things worse). Turns out that > even with ~100 parallel SVN operations the "system > > time" starts becoming significant/measurable (~10%). Both HTTP > (mod_dav_svn) and "svnserve" protocols participate > > in the lock contention. > > > > Your help would be greatly appreciated. > > > > Whew. So. Reducing this issue to "use a more efficient lock" is not > going to work, and you provided far too little > > information to even attempt a diagnosis. For starters, I recommend > gathering as much info as possible (anonymised of > > course) about the server configuration, everything from httpd an > svnserve to the repository config and underlying > > filesystem, if possible. Getting stack traces of the "stuck" threads > would be necessary, too. Without knowing exactly > > what is happening, these kinds of problems are extremely hard to > understand, let alone fix. > > Plus depending on which part of the code requires this lock a different > locking mechanism that might suit better for > this use case can possibly be chosen via configuration changes (e.g. httpd > allows this for most of its locking). > That would be awesome! I'll definitely try to get those stack tracebacks. Cheers. Doug -- *DOUGLAS B ROBINSON* SENIOR PRODUCT MANAGER T +1 925 396 1125 *E* doug.robin...@wandisco.com -- * <http://wandisco.com/>* **The *LiveData* Company *Find out more *wandisco.com <http://wandisco.com/>* <https://www.wandisco.com/liveanalytics> THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY AND MAY BE PRIVILEGED * If this message was misdirected, WANdisco, Inc. and its subsidiaries, ("WANdisco") does not waive any confidentiality or privilege. If you are not the intended recipient, please notify us immediately and destroy the message without disclosing its contents to anyone. Any distribution, use or copying of this email or the information it contains by other than an intended recipient is unauthorized. The views and opinions expressed in this email message are the author's own and may not reflect the views and opinions of WANdisco, unless the author is authorized by WANdisco to express such views or opinions on its behalf. All email sent to or from this address is subject to electronic storage and review by WANdisco. Although WANdisco operates anti-virus programs, it does not accept responsibility for any damage whatsoever caused by viruses being passed.
