-
Improvement
-
Resolution: Fixed
-
Minor
In a busy system with many quick jobs/saves (e.g. maven multi module projects!) then the master effectively becomes one big bottleneck as the OldDataMonitor is called on each new save and this uses a lock serializing all write requests.
The code should be investigated to see if either it can be made lockfree or at least reduce the scope of the locks.
- is related to
-
JENKINS-20702 Delete old data fails with ConcurrentModificationException
-
- Resolved
-
[JENKINS-30139] OldDataMonitor makes Jenkins single threaded for all saves.
Assignee | New: Stephen Connolly [ stephenconnolly ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Code changed in jenkins
User: Stephen Connolly
Path:
core/src/main/java/hudson/diagnosis/OldDataMonitor.java
http://jenkins-ci.org/commit/jenkins/2c5deeb6c061a91aeac232e978756de3b1d0be98
Log:
JENKINS-30139Switch from a big fat lock to a concurrent collection