Great to hear. Really appreciate the feedback!
On Thu, 23 May 2024, 15:39 'Hans Dampf' via go-cd,
wrote:
> So we have been running the new version for a couple of days now, and I
> can't see any further problems with it. The performance is great with >1000
> Pipelines now.
> It is a really
So we have been running the new version for a couple of days now, and I
can't see any further problems with it. The performance is great with >1000
Pipelines now.
It is a really great improvement.
Wolfgang Achinger schrieb am Montag, 13. Mai 2024 um 10:30:42 UTC+2:
> I'm currently in the
I'm currently in the process of upgrading the server and agents of all our
gocd setups. We will monitor it the next few days and I will come back if
we notice anything
Am Mo., 13. Mai 2024 um 10:24 Uhr schrieb Chad Wilson <
ch...@thoughtworks.com>:
> Great to hear - back to how it was *supposed*
Great to hear - back to how it was *supposed* to behave! I hope it hasn't
caused any other regressions
Now that this is cleaned up, let me know if it exposes any other unexpected
weird slowness you can't get to the bottom of and I'll see if I can chip
away at the other various niggles.
-Chad
Dude the fix is amazing !
Am Mo., 13. Mai 2024 um 04:05 Uhr schrieb Chad Wilson <
ch...@thoughtworks.com>:
> Apologies for the slow release of this (been rather busy personally) but
> 24.1.0 is out with what I think should be a fix for this issue.
>
> If you have any feedback it'd be
Apologies for the slow release of this (been rather busy personally) but
24.1.0 is out with what I think should be a fix for this issue.
If you have any feedback it'd be appreciated.
-Chad
On Mon, 19 Feb 2024, 15:15 'Wolfgang Achinger' via go-cd, <
go-cd@googlegroups.com> wrote:
> Hello,
>
>
> can you confirm how many agents and pipelines are mapped to the
environment below?
Yes that is true
Am Sa., 17. Feb. 2024 um 18:08 Uhr schrieb Chad Wilson <
ch...@thoughtworks.com>:
> Hiya folks
>
> I've been able to replicate this problem and should be able to fix it for
> a subsequent
Hello,
this is actually incredible news for us. We will look forward to the
release with the fix.
Thanks for the support.
The workarounds seem not to be viable for us, since we use the environment
for a lot of global variables and customizations.
Regards
Am Sa., 17. Feb. 2024 um 18:08 Uhr
Hiya folks
I've been able to replicate this problem and should be able to fix it for a
subsequent release - thanks for the help debugging.
The problem appears to arrive when there is a large number of pipelines*
mapped to an environment;* and also a large number of agents for that
environment.
> By 'resources' I am referring to the GoCD functionality where you can tag
agents with resources that they offer, which are then matched to pipeline
jobs that say they *require* those resources to run as part of agent
assignment.
10 Agents have 5 resources attached
85 have 1 resource attached
We
Cool, thanks! Just trying to gather enough information to see if I can
replicate or find the issue in a dedicated chunk of time this weekend.
You can email it to me, and/or encrypt with my GPG key if you'd like (
https://github.com/chadlwilson/chadlwilson/blob/main/gpg-public-key.asc)
By
> And how many resources are defined across the agents?
What exactly do you mean here? System resources? XMS XMX Values of java ?
- Is this a problem that has always been there, or something that has
changed with a GoCD version or other change in environment?
No we use this setup no for about a
And how many resources are defined across the agents?
Can you please answer the earlier questions I asked as well? It's rather
difficult to efficiently help if you don't respond to the questions that
characterise the problem from a maintainer perspective. :-)
- Is this a problem that has always
1 environment
164 materials
0 elastic agents
2 config repos
0 artifact stores
0 pluggable scms
Am Do., 15. Feb. 2024 um 15:01 Uhr schrieb Chad Wilson <
ch...@thoughtworks.com>:
> How many distinct environments and resources do you have across these 1200
> pipelines, roughly?
>
> On Thu, Feb 15,
How many distinct environments and resources do you have across these 1200
pipelines, roughly?
On Thu, Feb 15, 2024 at 5:38 PM 'Wolfgang Achinger' via go-cd <
go-cd@googlegroups.com> wrote:
> Additional information
> Since the pipelines are configured via ~150 yaml files.
> I tested it now with
Additional information
Since the pipelines are configured via ~150 yaml files.
I tested it now with one big, merged config file with all pipelines
But this did not change anything,
performance slow.
--
You received this message because you are subscribed to the Google Groups
"go-cd" group.
To
For comparison, that's a call of our oldest setup with 60 agents but a lot
less builds/pipeline
It is a lot faster.
[image: oldsetup.png]
Am Mo., 12. Feb. 2024 um 17:13 Uhr schrieb Chad Wilson <
ch...@thoughtworks.com>:
> Hi Hans
>
> Is this slowness specific to builds that are currently
Hi Hans
Is this slowness specific to builds that are currently running? Or is the
slowness (and speed up with deleted agents) the same even with
builds/stages that are no longer running (even if the agents are)?
Anything majorly different about this GoCD server setup compared to the
others, e.g
Hello,
we notice slow loads in the gui when you open the popup of a stage. The
loading animation in the popup takes 5-6 seconds on every stage, and we try
to narrow down why.
What we know so far is if we disable *and* delete all agents in the gui the
loading is instant. With the agents
19 matches
Mail list logo
