The job in the original picture showed only 7 items in its history.  Are
some of your jobs retaining many, many history entries?  If so, that will
slow the Jenkins startup time, and might slow the time to compute changes.
The configuration slicing plugin is very effective at showing (and
changing) the amount of history retained for all jobs in the system.

Has the file system changed any significant characteristics (switched from
a local fast file system to a USB 2.0 file system, or to a storage area
network or to an NFS mount, or some other form of remote file system)?

Is the slower performance specific to a few jobs, or general to all jobs?
If specific to a few jobs, then you might investigate if the workspace
directories for those jobs would benefit by being "wiped" (using the "Wipe
workspace" additional behaviour of the git plugin) and reconstructed the
next time the job runs.

The job in the original picture showed "Git polling log" as one of the
links.  If you're using git, did you change the git version at the same
time you updated Jenkins?  Command line git is generally very fast to
compute changes, so this is an unlikely scenario.

You could check the "raw git" performance in those repositories by changing
into the workspace directory of one or more jobs and executing "git log"
commands of various forms to confirm that command line git is performing
well.

Mark Waite

On Thu, Aug 25, 2016 at 4:48 AM Ravalika <pren...@gmail.com> wrote:

> I have tried applying the workaround mentioned for SECURITY-243, but no
> luck
> When i click on recent changes, still takes approx 15 min to display the
> messages.
>
> Thank you
> Renuka
>
>
> On Thursday, August 25, 2016 at 11:26:13 AM UTC+5:30, Ravalika wrote:
>>
>> Thank you,
>> Old Jenkin version is 1.6.3 migrated to jenkins stable version 2.7.1
>>
>>
>> On Monday, August 22, 2016 at 4:54:44 PM UTC+5:30, Daniel Beck wrote:
>>>
>>> When asking about a possible regression, it helps to mention both the
>>> version you're using now, as well as the version you were using before.
>>>
>>> Try applying the workaround mentioned for SECURITY-243 here:
>>>
>>>
>>> https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11
>>>
>>>
>>> > On 22.08.2016, at 08:42, Renuka Pampana <pre...@gmail.com> wrote:
>>> >
>>> > Hi,
>>> >
>>> > We have migrated recently to Jenkins new stable version. After
>>> migration, Jenkins takes too long for displaying the changes of the current
>>> job (approx. 15min).
>>> >
>>> > Can you please provide me some suggestions to improve the speed?
>>> >
>>> >
>>> > Thanks,
>>> > Renuka
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-use...@googlegroups.com.
>>> > To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/283e63c8-5cd2-459c-8161-0dc951383333%40googlegroups.com.
>>>
>>> > For more options, visit https://groups.google.com/d/optout.
>>> > <Capture.PNG>
>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/d4ebe6bc-9eba-4e0e-bc1a-1af6be7cf0af%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/d4ebe6bc-9eba-4e0e-bc1a-1af6be7cf0af%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHVJssX6ku3sbqrnEvZL2GD%2Bb-VNEr4Gr4J2hDE3C-LOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to