[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
Thorsten Heit started work on JENKINS-13547 Jenkins runs extremely slow with remote crowd server Change By: Thorsten Heit (18/Jun/12 11:26 AM) Status: Open In Progress 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
[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
Joel Pearson edited a comment on JENKINS-13547 Jenkins runs extremely slow with remote crowd server There's already a patch contained in the master branch contributed by John Crawford for exactly that Awesome looking forward to it 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
[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
Joel Pearson commented on JENKINS-13547 Jenkins runs extremely slow with remote crowd server .bq There's already a patch contained in the master branch contributed by John Crawford for exactly that Awesome looking forward to it 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
[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
Thorsten Heit commented on JENKINS-13547 Jenkins runs extremely slow with remote crowd server Surely there is a better way? Maybe there should be an option to allow crowd to wait until the session times out or something? I'm guessing checking every request is just to see if the account is still allowed to login to Jenkins? There's already a patch contained in the master branch contributed by John Crawford for exactly that AFAICT the Crowd libraries themselves have a feature to let you skip the validation for a certain amount of time. The plugin itself so far doesn't make use of this, i.e. each request to be processed gets validated against Crowd. In the next version you'll be able to specify that validation interval time. 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
[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
Joel Pearson commented on JENKINS-13547 Jenkins runs extremely slow with remote crowd server Indeed. The plugin is implemented as a servlet filter that checks the validity of the session on each request that is being processed. Surely there is a better way? Maybe there should be an option to allow crowd to wait until the session times out or something? I'm guessing checking every request is just to see if the account is still allowed to login to Jenkins? 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
[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
[
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
[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
[
https://issues.jenkins-ci.org/browse/JENKINS-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163608#comment-163608
]
Thorsten Heit commented on JENKINS-13547:
-
{quote}It seems like that every request to Jenkins gets authenticated to Crowd
or something like that.{quote}
Indeed. The plugin is implemented as a servlet filter that checks the validity
of the session on each request that is being processed.
{quote}The original Crowd plugin does not have this problem and does not affect
the performance of Jenkins in any visible form.{quote}
The original Crowd plugin contains a hardcoded session validation interval time
of 5 minutes. See
[https://github.com/jenkinsci/crowd-plugin/blob/master/src/main/java/com/ds/tools/hudson/crowd/CrowdSecurityRealm.java],
method "createSecurityComponents()"
> 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
[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
[ https://issues.jenkins-ci.org/browse/JENKINS-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163476#comment-163476 ] Thomas Lehmann commented on JENKINS-13547: -- 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. It's much better, but even not so fast as connecting directly to $JENKINS_HOST. It's not clear why Jenkins slowed down so much when activationg Crowd (the forwarding config did not change inbetween). 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. Is that normal? > 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
[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
[
https://issues.jenkins-ci.org/browse/JENKINS-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163107#comment-163107
]
Thomas Lehmann edited comment on JENKINS-13547 at 5/23/12 11:56 AM:
Our configuration:
{quote}
CentOS 5.8 SunJDK 1.7.0_03-b04 on x86-64
Jenkins 1.462
Crowd 2 integration 1.4
{quote}
{quote}
Against Crowd 2.4.2
{quote}
All other atlassian applications run quiete fast.
was (Author: tholewebgods):
Our configuration:
CentOS 5.8 SunJDK 1.7.0_03-b04 on x86-64
Jenkins 1.462
Crowd 2 integration 1.4
Against Crowd 2.4.2
All other atlassian applications run quiete fast.
> 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
[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
[ https://issues.jenkins-ci.org/browse/JENKINS-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163107#comment-163107 ] Thomas Lehmann commented on JENKINS-13547: -- Our configuration: CentOS 5.8 SunJDK 1.7.0_03-b04 on x86-64 Jenkins 1.462 Crowd 2 integration 1.4 Against Crowd 2.4.2 All other atlassian applications run quiete fast. > 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
[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
[ https://issues.jenkins-ci.org/browse/JENKINS-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163106#comment-163106 ] Thomas Lehmann commented on JENKINS-13547: -- I can confirm this bug in an intranet application. Since I've activated security with crowd authentication through the crowd2 plugin Jenkis is extremely slow. It takes upto 10 seconds to load the overview or a configuation page. Even opening the conextmenus takes 3-4 seconds when hovering context sensitive links. IMO this is unusable. Really! I'll try to debug this these days to tisolate the problem, but I'm sure this is related to the crowd2 plugin. > 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
[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
[ https://issues.jenkins-ci.org/browse/JENKINS-13547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Pearson updated JENKINS-13547: --- Priority: Critical (was: Major) > 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
[JIRA] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
Joel Pearson created JENKINS-13547: -- Summary: 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 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
