-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JENKINS-50429 combine env vars into a single set before writing once #393
Conversation
mrjgreen
commented
Oct 31, 2018
- combine env vars before writing once into the container
@carlossg - I tested this locally and it appears to have cut the time down to 1 second overhead instead of 3/4 seconds. As far as I can tell, the env vars are still being set... Does this look reasonable? |
makes sense. But I think I have tested something similar and didn't improve the speed, need to retest |
👍 - I've only tested this on a very simple test case. We are attempting to test it against a large pipeline soon. Is there anything we can do to address the root cause of the problem with the input.write() buffer? Would upgrading the JDK version in the jenkins containers be likely to help?
I've had a quick look into this and it doesn't seem like this was ever resolved: |
Was wondering if there was any other progress against this? |
Our tests suggest that this does reduce the overhead of running sh commands - it reduced the overhead of a This is still not ideal. I think the problem needs raising with the fabricate K8s client to see if we can use an alternative to the Input Stream (which is where the problem originates). |
also wondering if there was any other progress against this.... |
Better than asking for progress it'd be good if you tried the pr and comment on whether it fixes the problem for you or not |
I have tested with this job and I'm still getting a big difference between shell execution inside a container.
|
Merging because it doesn't hurt |