[
https://issues.jenkins-ci.org/browse/JENKINS-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163611#comment-163611
]
Thorsten Heit commented on JENKINS-13547:
-----------------------------------------
{quote}Update. We've isolated the problem.
Jenkins speed up dramatically when changing the apache's configuration.
Previously our Apache was configured using mod_jk via AJP.
We got aware of this after connecting to the Jenkins machine's port directly
which worked quiet fast.
Now we've configured it to use mod_proxy.{quote}
Strange. What versions of Apache, mod_jk and mod_proxy do you use?
BTW, I just found the following quite interesting documentation:
* https://confluence.atlassian.com/display/DOC/Running+Confluence+behind+Apache
* https://confluence.atlassian.com/display/DOC/Apache+and+Apache+Connector+Tips
{quote}It's much better, but even not so fast as connecting directly to
$JENKINS_HOST.{quote}
Sure. When you put Apache between your browser and Jenkins, you'll get more or
less overhead in the communication...
{quote}I've also noticed that there is constant traffic noise between the
JENKINS_HOST and the CROWD_HOST with about 2 connects per second. The traffic
does not correspond to any established connection from the browser to Jenkins
(I've expected this due to the AJAX polling). In other words: 0 requests per 10
secs from browser to Jenkins, ~20 connects per 10 sec from Jenkins to
Crowd.{quote}
Do you see any traffic between your browser and Jenkins?
> Jenkins runs extremely slow with remote crowd server
> ----------------------------------------------------
>
> Key: JENKINS-13547
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13547
> Project: Jenkins
> Issue Type: Bug
> Components: crowd2
> Environment: Centos/RHEL 6.2
> Jenkins 1.460
> Crowd 2.2.7
> Reporter: Joel Pearson
> Assignee: Thorsten Heit
> Priority: Critical
>
> When Crowd is running on a different continent to Jenkins, the performance of
> Jenkins is drastically affected, to the point that Jenkins is unusable.
> It seems like that every request to Jenkins gets authenticated to Crowd or
> something like that.
> The original Crowd plugin does not have this problem and does not affect the
> performance of Jenkins in any visible form.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
