You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2014/05/01 23:06:19 UTC

[jira] [Commented] (INFRA-7535) Jenkins UI responds very slowly

    [ https://issues.apache.org/jira/browse/INFRA-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986994#comment-13986994 ] 

Hervé Boutemy commented on INFRA-7535:
--------------------------------------

FYI, I started to record response time measured by curl on http://builds.apache.org/ once per hour, just to have simple figures on a long period of time

result is available here: http://people.apache.org/~hboutemy/builds/

> Jenkins UI responds very slowly
> -------------------------------
>
>                 Key: INFRA-7535
>                 URL: https://issues.apache.org/jira/browse/INFRA-7535
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Robert Munteanu
>            Priority: Critical
>
> Accessing the main Jenkins server can take a lot of time for day-to-day operations. Some examples:
> 1. Accessing a job ( https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/ ) : 9 seconds for a HEAD request using curl, 15+ seconds using Firefox
> 2. Accessing a job's configuration ( https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/configure ) : 15+ seconds using Firefox
> 3. Viewing a job's SVN polling log (https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/scmPollLog/) :  38 (!) seconds for a HEAD request using curl, 10 seconds using Firefox
> This greatly slows down the work done using Jenkins, so anything which makes the UI faster would be greatly appreciated.



--
This message was sent by Atlassian JIRA
(v6.2#6252)