Branch: refs/heads/jenkins-34213
Home: https://github.com/jenkinsci/remoting
Commit: 98a7e3a837853ab1e8bf8b008862ed5738378bfc
https://github.com/jenkinsci/remoting/commit/98a7e3a837853ab1e8bf8b008862ed5738378bfc
Author: Stephen Connolly <[email protected]>
Date: 2016-04-14 (Thu, 14 Apr 2016)
Changed paths:
M src/main/java/hudson/remoting/RemoteInvocationHandler.java
Log Message:
-----------
[JENKINS-34213] Collect and report meaningful stats, batch the reference
collection for better stability
- We want to report on these things only if they are an issue. Logging of the
actual stats should be below the radar of the users using a default logger
level of `INFO` provided that the Unexporter is not doing much
- When the Unexporter is busy (i.e. the m1 rate is > 100/sec) then we should
start reporting at `INFO`
- In the event that there is sustained high levels of work, we should alert the
user and recommend turning off the stack traces to reduce GC pressure
- My stress testing revealed that under very heavy load it is better to batch
the removal and then batch the clean-up even if this batching means that the
sweeps are not as frequent.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
