Exe runs very slow under Jenkins compared to running directly

[J Starbird]

Jenkins 2.19.1

Java 8

Windows 7 Pro Sp1

I don't know exactly when this started happening, at which upgrade of Jenkins it was just before moving to 2.x, but at some point an exe we use for special tests started running much slower. It went from running in 2hrs to taking over 6hrs. 

Nothing in the exe was changed, the only changes were to Jenkins and upgrading to Java 8. 

There are no errors reported anywhere, it simply just takes that much longer and ONLY when run under Jenkins. When I run this exe with the exact same params and on the exact same system it runs fine and back at it's normal length of time.

When monitoring the system it appears the exe is doing some IO at the time but under Jenkins it's just extremely slow at doing it.

I've gone from running the exe from and MSBuild project to running it directly as a Windows EXE and also using the Windows Batch, in every case it runs the same slow speed.

I've discussed it with other developers here and no one has any ideas so I'm now asking all of you, anyone have any ideas?

The system has 16Gb of ram, 8 assigned to Jenkins, it has plenty of disk space and it has 4 cores.  Nothing else is running on the system at the time, just Jenkins and the EXE. Antivirus is disabled, UAC is disabled, the user Jenkins runs as is full Admin on the system. 

Any help would be appreciated. Thanks.

[Daniel Beck]

Is it writing large amounts of text to stdout? I.e. the Jenkins build log? If so, is it still slow when redirecting output to a file, or NUL?

> --
> 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/37030984-def4-495a-ac57-e76e34242fd4%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[J Starbird]

No it doesn't write very much to stdout. Basically it just writes out what the params were that were passed into it and then it writes out a short progress tag, so like "Doing step 1" but it all only amounts to about 5 lines of text, short lines.

[Baptiste Mathus]

You probably want to understand what is happening during the execution. For that purpose, you want a thread dump of the running JVM: https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump

HTH

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8544807e-1ffc-40f3-8236-8d35723086aa%40googlegroups.com.