[JIRA] [accelerated-build-now] (JENKINS-22310) CLI slow performance investigation

Fri, 21 Mar 2014 14:08:21 -0700

I find the difference between DEV@cloud masters and ci.jenkins-ci.org rather stark. ping time to ci.jenkins-ci.org is about 80ms. Can't measure that for jenkins.ci.cloudbees.com as it doesn't respond to ping.

Here's the profiler measuring wall clock times and major contributors to the execution time:

CloudBees

  • CLI.main() total: 15.6sec
  • 1.0sec to getCliTcpPort
  • 0.5sec to connectViaCliPort
  • 2.7sec to authenticate
    • including about 1.6sec to get the result of authentication in c.readBoolean()
  • Request.call() spent 10secs

ci.jenkins-ci.org

  • CLI.main() total: 5.3sec
  • 1sec to getCliTcpPort
  • 0.5sec to connectViaCliPort
  • 1.5sec to authenticate
    • including 1.2sec to get the result back: c.readBoolean()
  • Request.call() spent 1.8sec

Request.call() is the time between the client sending the command to the server and the server returns from that sync call, and to my surprise this accounts for almost all the difference of the performance. I was initially suspecting a problem like chatty protocol , but it's starting to look like the issue is purely on the server side.

Next step: measure the performance on the server side.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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.

Reply via email to