systemtap analysis shows the Connection c_mutex is heavily contended - we should investigate ways to reduce locking
gets rid of op_thread_lock/cv - other improvements 0002-Ticket-514-investigate-connection-locking.patch
Looks good, but one question, shouldn't pb_q_size_max be initialized before comparing it to pq_q_size in add_pb? Or is a PRInt32 automatically set to 0?
Replying to [comment:6 mreynolds]:
C guarantees that static variables are initialized to 0 if not explicitly initialized.
0001-Ticket-514-investigate-connection-locking.patch 0001-Ticket-514-investigate-connection-locking.patch
commit 304502c Author: Rich Megginson rmeggins@redhat.com Date: Tue Feb 19 19:32:56 2013 -0700
Metadata Update from @rmeggins: - Issue assigned to rmeggins - Issue set to the milestone: 1.3.2 - 09/13 (September)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/514
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.