No sorry, maybe rtyler or kohsuke can give us an idea...

> Am 09.10.2013 um 06:42 schrieb Benjamin Lau <[email protected]>:
> 
> It seems to at least be running... but the performance characteristics
> are nothing like what I'm seeing on the machine I have at home.
> 
> Do you know anything about what kind of hardware ci.jenkins-ci.org is?
> 
> Ben
> 
>> On Tue, Oct 8, 2013 at 8:35 PM, Domi <[email protected]> wrote:
>> Hmm, this Job is still running, so i guess the change did not get us to a 
>> much better state yet :(
>> 
>>> Am 08.10.2013 um 19:48 schrieb Kohsuke Kawaguchi <[email protected]>:
>>> 
>>> 
>>> The sqlite database had about 4.3GB of data.
>>> 
>>> As per the instruction of Domi, we blew away that file and got the new one 
>>> running:
>>> 
>>> https://ci.jenkins-ci.org/view/Infrastructure/job/infra_statistics/94/console
>>> 
>>> This will take a quite a while to repopulate the database, but we'll see 
>>> how #95 will go.
>>> 
>>>> On 10/08/2013 10:19 AM, Kohsuke Kawaguchi wrote:
>>>> 
>>>> Wow! That was super quick!
>>>> 
>>>>> On 10/08/2013 12:13 AM, Benjamin Lau wrote:
>>>>> We need to add an index to the stats.db. I mailed Kohsuke privately
>>>>> that I was looking into this, but it turned out it wasn't to hard to
>>>>> solve most of the problem with the addition of the following index:
>>>>> 
>>>>> CREATE INDEX plugin_name on plugin (name);
>>>>> 
>>>>> https://github.com/jenkinsci/infra-statistics/pull/1
>>>>> 
>>>>> Enjoy!
>>>>> 
>>>>> Ben
>>>>> 
>>>>>> On Mon, Oct 7, 2013 at 9:06 PM, Kohsuke Kawaguchi <[email protected]> 
>>>>>> wrote:
>>>>>> For a while back, Domi wrote the code [1] that tallies anonymized usage
>>>>>> statistics and parse them into JSON files. This is what drives the plugin
>>>>>> installation count stats in Wiki.
>>>>>> 
>>>>>> We noticed that some time ago, this started taking very long time to run
>>>>>> [2]. Whereas it used to take an hour or so, now it can run upward of a 
>>>>>> whole
>>>>>> day!
>>>>>> 
>>>>>> This is causing a strain on the system, and it blocks other critical
>>>>>> infrastructure jobs from running in a timely fashion.
>>>>>> 
>>>>>> Can anyone look into the program and see what's causing the problem? Or
>>>>>> perhaps rewrite it so that it can run in a realistic amount of time?
>>>>>> 
>>>>>> 
>>>>>> [1] https://github.com/jenkinsci/infra-statistics
>>>>>> [2] https://ci.jenkins-ci.org/job/infra_statistics/buildTimeTrend
>>>>>> --
>>>>>> Kohsuke Kawaguchi
>>>>>> 
>>>>>> --
>>>>>> 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].
>>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>> 
>>> 
>>> --
>>> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
>>> Try Jenkins Enterprise, our professional version of Jenkins
>>> 
>>> --
>>> 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].
>>> For more options, visit https://groups.google.com/groups/opt_out.
>> 
>> --
>> 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].
>> For more options, visit https://groups.google.com/groups/opt_out.
> 
> -- 
> 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].
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
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].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to