Thanks for sharing!
For what it's worth the
https://github.com/gocd-contrib/docker-swarm-elastic-agent-plugin ha snot
been released for a long time. It probably works ok with respect to GoCD
interfaces (as these have not changed), but may or may not work correctly
with latest swarm features and
So we basically "fixed" our problem. The problem was mitogen scales awful
with multiple playbook on at the same time on the same machine. It seems it
does not support multicore CPU. CPU 1 on every server is always running at
100%, we suspect this is because mitogen only uses this one core for
What is a "workernode" in this context? This isn't GoCD terminology, so
it's unclear what this means?
GoCD agents simply fork processes to run your tasks within the 'go' user
context of the agent process. IIRC the entire "wrapping" environment from
the agent process should be propagated to the
Ok did more testing and build a new setup from scratch. As expected, the
performance was very good.
Then we moved one of the old "broken" workernodes from the old setup to the
new setup and unexpectedly the performance was also very good again.
So there seems to be some slowdown on the
> Is there maybe a cachefile or lockfile created by the agents which does
not get deleted with a deinstallation?
This might help find anything owned by the go user.
$ sudo find / -user go
- Ketan
On Thu, May 4, 2023 at 3:16 PM 'Hans Dampf' via go-cd <
go-cd@googlegroups.com> wrote:
>
> It's
It's not just one task, it's the whole playbook which is slower.
Local yes as user go.
This runs in a normal performance
go@host1:~$ ansible-playbook slowplaybook.yaml -i inventory
On the same machine the same playbook but executed by the go-agent is slow.
It ran fast in the past until the
It's unclear from your problem description if the entire job is taking
10-30 minutes, or the task is taking 10-30 minutes. You mention that
running locally from the agent is quick — it is unclear if you're running
your task as `go` user or `root` user. For context, there are other
overheads in
Hello,
our setup consists of 10 worker with 15 agents each. We run ansible +
mitogen on the agents. Currently, we have a problem with the go-agent +
mitogen.
Mitogen itself is a tool to speedup ansible runs by "tunneling" multiple
tasks over one ssh connection.
