Concourse extremely slow

EngineerBetter / concourse-up

Deprecated - used Control Tower instead

https://github.com/EngineerBetter/control-tower

Apache License 2.0

203 stars 28 forks source link

Concourse extremely slow #69

Closed aterreno closed 5 years ago

aterreno commented 5 years ago

Hi guys, we've been using concourse-up for more than a year and all good, but since the upgrade to 4.x everything got painfully slow.

I've opened this one https://github.com/concourse/concourse/issues/2604 but so far it only got ignored.

Additionally, we are unable (and I am not sure why) to ssh in the boxes, either downloading the private/pub keys from the json in s3 or with the command line setting up the env variables.

Can you help?

Thanks

danyoung commented 5 years ago

Hi @aterreno - Let's try to work this one out. Could you join us on Slack and we might be able to diagnose the issue? https://join.slack.com/t/concourse-up/shared_invite/enQtNDMzNjY1MjczNDU3LTA1NzIxYTZkYjFkMjA2ODBmY2E2OTM3OGE3YTc2OGViNTMxYTY4MjYwNGNjOTAxNDNiOGE5NzhmMTQ2NWVhNzQ

aterreno commented 5 years ago

Adding context and infos as we progress this on Slack.

Cpu at 40+% on idle (no jobs running)

Recreating the worker didn't change the situation, cpu is at min (not even avg) at 40+%

concourse.worker.0-20180927-104150-734269313.zip

Attached logs of worker when idle.

aterreno commented 5 years ago

Closing this one up for now, as performances improved substantially by removing the npm-repo-cache resource from all my pipelines (20~)