Can you tell us more about the hardware used?
On Tue, 13 Oct 2015 at 9:29 PM, Michael Neale <[email protected]>
wrote:

> Yes recently I have heard rumblings about fingerprints and other accreted
> files over time.
>
> Looking at the variation of times people see, I am questioning the utility
> of a generic test suite. Things vary so much there may be too many
> variables at play to make something like this useful right now. It's
> certainly useful to profile specific cases when people have a problem, and
> it's great there have been recent improvements (eg Apache example), but it
> may be a bit hard to justify right now.
>
>
> On Fri, 9 Oct 2015 at 8:29 PM, Robert Sandell <[email protected]>
> wrote:
>
>> A theory of mine is that startup times can depend on how "old" your build
>> records are, if there needs to be a lot of conversion of old data
>> structures in new plugin versions that could have a measurable impact,
>> maybe even OldDataMonitor gets involved and slows things down.
>>
>> So there could be a difference in generated test data vs. "real world"
>> data where it has grown over time.
>>
>> /B
>>
>> On Fri, Oct 9, 2015 at 11:15 AM, James Nord <[email protected]> wrote:
>>
>>> So I actually tried creating test data a year or so ago (maven job type
>>> with a large number of sub modules) and creating several of them in folders
>>> - but I never saw the issues (3 hour cold startup time) I was seeing on the
>>> production instance :(
>>>
>>> Maven project is available at
>>> https://github.com/jtnord/maven-test-project if you want to experiment.
>>>
>>> It may well have been around fingerprinting as my fingerprint file on
>>> production was > 2GB
>>> but I invested in some better storage and got the startup to under 3
>>> minutes so no longer had the inclination to try any further...
>>>
>>> On Wednesday, October 7, 2015 at 12:29:47 AM UTC+2, Michael Neale wrote:
>>>>
>>>> Yes that would be quite interesting. A stand alone tool could be
>>>> useful. There are lots of things to measure but generating a lot of noise
>>>> and jobs would be a great start. When you say "job upload" what were you
>>>> measuring?
>>>> On Fri, 2 Oct 2015 at 9:59 PM, Vojtech Juranek <[email protected]>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> > Is this something people would be interested in?
>>>>>
>>>>> yes, sounds interesting
>>>>>
>>>>> > Having either large sample JENKINS_HOME specimens or test code that
>>>>> can
>>>>> > generate pathological data would be required, as well as automation
>>>>> around
>>>>> > running it on a variety of machines (not necessarily cloud, ideally
>>>>> want to
>>>>> > be testing code not cloud infrastructure).
>>>>>
>>>>> IMHO it's better to have some code do generate various type of
>>>>> workspaces and
>>>>> loads - same as in the mentioned presentation, you should check
>>>>> performance
>>>>> characteristics for various job types, log sizes, number of plugin
>>>>> used etc.
>>>>> Using one big workspace can be harder to understand as it can combine
>>>>> multiple
>>>>> issues together and you can end up with tuned Jenkins which works fine
>>>>> with
>>>>> this use case, but performs not that well with other use cases.
>>>>>
>>>>> I did very simple job generator of freestyle jobs [1] for PerfCake [2]
>>>>> to
>>>>> measure responsiveness of job upload in the past. If you are
>>>>> interested, I can
>>>>> updated it to generate various jobs or it can be done in any other
>>>>> tool you
>>>>> prefer (or standalone application if you like).
>>>>>
>>>>> Cheers
>>>>> Vojta
>>>>>
>>>>> [1]
>>>>> https://github.com/vjuranek/jenkins-perf-tests/blob/master/perfcake/src/main/resources/scenarios/create-freestyle.xml
>>>>> [2] https://www.perfcake.org/
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to a topic in the
>>>>> Google Groups "Jenkins Developers" group.
>>>>> To unsubscribe from this topic, visit
>>>>> https://groups.google.com/d/topic/jenkinsci-dev/1F9DHyMOutw/unsubscribe
>>>>> .
>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>> [email protected].
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/1541911.yeAEkfGOKe%40localhost.localdomain
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>> --
>>>
>> You received this message because you are subscribed to the Google Groups
>>> "Jenkins Developers" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to [email protected].
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/06f87cca-9af7-4624-90d2-6b85516e3eb0%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/06f87cca-9af7-4624-90d2-6b85516e3eb0%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Robert Sandell
>> *Software Engineer*
>> *CloudBees Inc.*
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-dev/1F9DHyMOutw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS0Ee2W0nsZyhU3-tAdn3vjEDa7Tue_D7d0VA%3DcVMAvSww%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS0Ee2W0nsZyhU3-tAdn3vjEDa7Tue_D7d0VA%3DcVMAvSww%40mail.gmail.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 Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAKVMTi7zvHT785zMmqqR6kMv_X5kJa8Pj1-dcgbZ6U7xCU-cAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to