Folks: >From a Subversion user:
“... we have very high concurrent connections to Subversion that seem to crater Subversion. The SVN Serve process we use to access the Subversion repository is using the “svn” protocol by our “system user”, mostly read-only. Then, we, on behalf of the user make request to Subversion using the “http” protocol to fetch their data. So we have lots of connections to Subversion. But the volume of concurrent requests over the “svn” protocol cause the “svnserve” process to consume CPU cycles in a kernel “mutex-lock” which is implemented using “spin locks”. The “svnserve” process makes the mutex calls using the “apache” (APR) semaphore wait calls, but on Linux this is a “mutext-lock” request.” So is there a better, more scalable, semaphore that can be used? 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.