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 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 # of agents in the DB (deleted or not) or # of pipeline runs or
> configuration/version - that type of thing?
>
> To narrow things down a bit more, it's worth opening your browser Inspect
> and looking at the network tab when clicking the button and seeing which of
> the requests are slow:
>
> [image: image.png]
>
> On the assumption that it's the server that's slow rather than the UI,
> that will at least tell us which API is slow, and thus which code path or
> DB queries to look at contributing to the 5-6 seconds (or whether it is all
> of them).
>
> If it's much faster when the agents are deleted, my guess is that it could
> be to do with the logic to essentially allow the agents to be linked, but I
> am not sure intuitively which logic that might be.
>
> -Chad
>
> On Mon, Feb 12, 2024 at 11:19 PM 'Hans Dampf' via go-cd <
> go-cd@googlegroups.com> wrote:
>
>> 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 registered (imported db table
>> "agents"), the load time is back to several seconds.
>>
>> Gocd does the following sql statment in the database. 'update agents set
>> deleted=true where uuid in("alot uuids")'
>>
>> If I execute the statement directly in the database, it does not increase
>> the performance. You have to delete the agents via gui.
>>
>> The database backend is a postgres 14.
>> We have several other gocd setups on the same databaseserver without this
>> problem.
>>
>> The setup consists of 19 agent-servers with 5 agents each, overall 95
>> agents.
>> Every agent did process ~ 15000 stages so far.
>>
>> I haven+t figured out at the moment what exactly gocd does during the
>> creation of the popup. But it must have something to do with the agents
>> and/or the agent runtime history.
>>
>> Maybe someone can point me in the right direct where the bottleneck could
>> be.
>>
>> Regards
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "go-cd" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to go-cd+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/go-cd/502ce13f-1696-490c-aa91-6ca542f7e78cn%40googlegroups.com
>> <https://groups.google.com/d/msgid/go-cd/502ce13f-1696-490c-aa91-6ca542f7e78cn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "go-cd" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/go-cd/c1n1Aq7hG1k/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/CAA1RwH-wCHVD9UJQ_ZPXMkXWKRi6vsLRR9tMMFdAZMiTk6hySQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/go-cd/CAA1RwH-wCHVD9UJQ_ZPXMkXWKRi6vsLRR9tMMFdAZMiTk6hySQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CANhjCLBa4wK3tYe6FLvLTOY-CiU9jjixaVDwgBicyDADqR2wcQ%40mail.gmail.com.

Reply via email to