Looks like it's not using Java7. Let me tweak the setting.


On 10/17/2013 09:54 AM, Benjamin Lau wrote:
Thanks!

It's in the queue... I'll take a look later.

username: netjunki

Ben


On Thu, Oct 17, 2013 at 9:42 AM, Kohsuke Kawaguchi
<[email protected]> wrote:

Done and started #98.

What is your jenkins-ci.org account? We should let you configure this job
directly.


On 10/17/2013 01:01 AM, Benjamin Lau wrote:

So this job is still taking a very long time to run. It looks like the
last run pulled a new version of Java 7... could we add a call to
groovy --version somewhere to see what version of Java 7 it's actually
picking up?

Thanks!

Ben

On Tue, Oct 15, 2013 at 1:18 AM, Benjamin Lau <[email protected]>
wrote:

Using Oracle's Java 7u40 on OS X:
time groovy createJson.groovy
real    4m2.384s user    0m40.201s sys    0m28.804s

Using Oracle's Java 7u25 on OS X:
time groovy createJson.groovy
real    6m26.936s user    0m43.045s sys    0m46.805s

Any idea what version of the JDK and what OS ci.jenkins-ci.org is
running?

Ben

On Mon, Oct 14, 2013 at 2:43 PM, Benjamin Lau <[email protected]>
wrote:

if I understand correctly output of #96, import was skipped and I
understand
that update of 800+ files takes some time. But if my observation was
correct
(therefore I asked for timestamper plugin to have some evidence), it
was stuck
on one single SQL query for several hours - this is what I don't
understand
and seems really strange to me


Well... the indexes are there if you want to check. Just download the
stats.db from the workspace... though I'm guessing Domi and Kohsuke
don't really want a ton of people doing that... since it's almost
6GB... but it's that big now because it includes a bunch of indexes.

I'm currently rerunning timing tests locally on my machine using Java
7u40 to see if I can repro the issue on my own box. But I can run the
whole generating the json output process in about 2 minutes on my
laptop with Java 6. The data import is pretty slow no matter what
since it has to read and process a bunch of huge json files... The
indexing definitely helped the issue since before those were added the
process didn't complete in over 600 minutes.

Ben




--
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.



--
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.

Reply via email to