daniels changed the topic of #freedesktop to: https://www.freedesktop.org infrastructure and online services || for questions about freedesktop.org projects, please see each project's contact || for discussions about specifications, please use https://gitlab.freedesktop.org/xdg or xdg@lists.freedesktop.org
privacy has quit [Remote host closed the connection]
vyivel has quit [Remote host closed the connection]
vyivel has joined #freedesktop
ximion has joined #freedesktop
___nick___ has joined #freedesktop
todi has quit [Remote host closed the connection]
todi has joined #freedesktop
<emersion>
> But given that our db is 90% CI, this split should hopefully speed up the instance quite a bit by having normal operations handled on a much smaller db.
<emersion>
unless we have the DB currently overloaded i'm not sure it would change anything
scrumplex has joined #freedesktop
scrumplex_ has quit [Ping timeout: 480 seconds]
privacy has joined #freedesktop
f_ has quit [Ping timeout: 480 seconds]
___nick___ has quit []
___nick___ has joined #freedesktop
___nick___ has quit []
<bentiss>
emersion: that would still give us twice the db connections available, hopefully :-)
<emersion>
but is that a bottleneck atm?
___nick___ has joined #freedesktop
<bentiss>
when we had the spam users created as a wave, the UI felt very sluggish
<vyivel>
i thought sluggish ui was a gitlab feature
<bentiss>
but TBH, I think what makes things hard for the cluster are the backups, as we are compressing and sending a lot of Giga bytes everyday (the backups of gitaly takes between 13 to 15 hours to complete)
vx has quit [Quit: G-Line: User has been permanently banned from this network.]
vx has joined #freedesktop
alanc has quit [Remote host closed the connection]
alanc has joined #freedesktop
privacy has quit [Quit: Leaving]
Haaninjo has joined #freedesktop
alyssa has joined #freedesktop
<alyssa>
bentiss: Is there a non-neglible chance of downtime on June 5?
f_ has joined #freedesktop
<alyssa>
No worries if so - just need to know if I should setup a non-fd.o mirror in case the downtime is a bit longer than expected
<alyssa>
...and thank you in advance for the upgrade ^^
<bentiss>
alyssa: technically it shoudn't be with much risks, but we never know. Thus the 48h delay, as I expect this to be more like 12-24h. But given that the split of teh db consists in taking another snapshot of the db, and re-replicating it in a second postgres instance, and then clearing up the 2 dbs, I suspect this will take at least twice the usual time, so 24h is not unexpected
<bentiss>
48h should be in case something goes wrong, and we had to redeploy the backup. So I think we can make that decision on Monday evening here on Tuesday morning and we'll let folks know
<alyssa>
sounds great, thanks! and good luck :)
Haaninjo has quit [Quit: Ex-Chat]
AbleBacon has joined #freedesktop
___nick___ has quit [Ping timeout: 480 seconds]
___nick___ has joined #freedesktop
<daniels>
bentiss: should we downgrade gitaly backups to 2x/wk?
<bentiss>
daniels: that's a good idea actually
<bentiss>
not sure we need a daily backup given the history
<bentiss>
maybe we could rotate them as well, gitaly-0, then -1 then -2 and then -3, which roughly gives 2x/week, but one everyday :)