Used by multibranch pipeline and possibly by pipeline as far as I recall.

On Fri, Feb 8, 2019, 5:52 PM Calvin Park <calvinsp...@gmail.com wrote:

> It seems to contain some sort of git cache. Thankfully(?) all the
> directories are empty.
>
>> /mnt/nfs/jenkins_home$ ls caches/
>> git-0d341dcbcc7c33c4efc44a104b892b60
>> git-79660c3529cacbdbe1ac71b7c36e1a3f
>> git-0d341dcbcc7c33c4efc44a104b892b60@tmp
>> git-79660c3529cacbdbe1ac71b7c36e1a3f@tmp
>> git-0fba0b0ccfb8c3ca2809f860ea497fbf
>> git-84f1d58c7f2dde1b560bd3471e85cf5f
>> git-0fba0b0ccfb8c3ca2809f860ea497fbf@tmp
>> git-84f1d58c7f2dde1b560bd3471e85cf5f@tmp
>> git-117076ea5a481ebdd2beea321164041c
>> git-93d0b594de0d6af9e1ac33ea8dd03742
>> git-117076ea5a481ebdd2beea321164041c@tmp
>> git-93d0b594de0d6af9e1ac33ea8dd03742@tmp
>> git-20faeeea626404c43e0af02b3443a0ca
>> git-bedd02d2756f33f2b6dd8e496041e9a5
>> git-20faeeea626404c43e0af02b3443a0ca@tmp
>> git-bedd02d2756f33f2b6dd8e496041e9a5@tmp
>> git-6637777a4358cb957136aec86030ea76
>> git-ca5af9d29c97e0a07af654ef31dbcd93
>> git-6637777a4358cb957136aec86030ea76@tmp
>> git-cde48c33a9866d69b3dab200ae527b91
>> git-6c18e173e843c139db9b4bcd2949c277
>> git-cde48c33a9866d69b3dab200ae527b91@tmp
>> git-6c18e173e843c139db9b4bcd2949c277@tmp
>> git-ea66c44ab8389abea26eb7f2f93ee8d0
>> git-72cee31ae083a2db1f8fb009bcf624ed
>> git-ea66c44ab8389abea26eb7f2f93ee8d0@tmp
>> git-72cee31ae083a2db1f8fb009bcf624ed@tmp
>
>
>
> In order to minimize the performance hit from putting jenkins_home on NFS,
> I'm trying to find the directories which are frequently accessed
> directories and has many small files
>
>> /mnt/nfs/jenkins_home$ ls -d */
>> .cache/          ?
>> .groovy/         ?
>> .java/           ?
>> caches/          ?
>> config-history/
>> fingerprints/
>> init.groovy.d/
>> jobs/
>
>      builds/     moved out to local disk and not backed up
>>      workspace/  moved out to local disk and not backed up
>
> logs/
>>
> nodes/
>> plugins/   moved out to local disk and not backed up
>> secrets/
>> updates/
>> userContent/
>> users/
>> war/   moved out to local disk and not backed up
>> workflow-libs/
>>
>
> What are some of the other directories in here that I can/should move out
> of NFS? Ideally they should be ephemeral and frequently accessed.
>
> Thank you
>
>
>
> On Tuesday, February 5, 2019 at 6:08:46 AM UTC-8, Baptiste Mathus wrote:
>>
>> I've had a quick look, and I'm not sure I ever saw a caches directory
>> under JENKINS_HOME (this is very possible I just don't remember).
>> Can you possibly list what's in there so we can try and understand what
>> is generating this directory?
>>
>> We segregate data quite aggressively already in Evergreen and I do not
>> remember of such a directory/option.
>>
>> https://github.com/jenkins-infra/evergreen/blob/master/distribution/Dockerfile#L22-L34
>>
>> Thanks
>>
>> Le dim. 3 févr. 2019 à 00:44, Calvin Park <calvi...@gmail.com> a écrit :
>>
>>> I'm running $JENKINS_HOME on NFS. Due to the performance penalty,
>>> I want to move out as many temp directories as I can to local disk.
>>>
>>> Thus far I've moved
>>>
>>>    -
>>>    
>>> -Djenkins.model.Jenkins.workspacesDir='/local_cache/workspace/${ITEM_FULL_NAME}'
>>>    - --webroot=/local_cache/web
>>>    - --pluginroot=/local_cache/plugin
>>>
>>> In $JENKINS_HOME there's caches directory which seems like an obvious
>>> choice to move out.
>>>
>>>    1. Is there a way to configure the location for $JENKINS_HOME/caches?
>>>    2. What are other directories that can be recreated, thus can be
>>>    moved out of the NFS?
>>>
>>> Thanks!
>>>
>>> --
>>> 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/6a923fd6-da83-484e-b57c-c899e08a56f3%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/6a923fd6-da83-484e-b57c-c899e08a56f3%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/998a1e68-9e5a-48e2-b1eb-389e6b5b4652%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/998a1e68-9e5a-48e2-b1eb-389e6b5b4652%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/CAO49JtGm0ZvYkyS7VaX%2BEd8807dwAr47WK%3DE-YfmR9GStx3e3g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to