[Libre-soc-bugs] [Bug 1162] New: change git mirror sync period

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Mon Sep 18 20:03:37 BST 2023


https://bugs.libre-soc.org/show_bug.cgi?id=1162

            Bug ID: 1162
           Summary: change git mirror sync period
           Product: Libre-SOC Website
           Version: unspecified
          Hardware: PC
               URL: https://salsa.debian.org/Kazan-team/mirrors
                OS: Linux
            Status: IN_PROGRESS
          Severity: enhancement
          Priority: ---
         Component: website
          Assignee: programmerjake at gmail.com
          Reporter: programmerjake at gmail.com
                CC: libre-soc-bugs at lists.libre-soc.org, lkcl at lkcl.net,
                    programmerjake at gmail.com
   NLnet milestone: ---

https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-September/005649.html

<lkcl at lkcl.net> wrote:
>
> please reduce that to 24 hours. i was not in any way consulted
> on this decision and the server being mirrored is in no position
> to sustain massive loading, plus i have to pay (personally)
> for the bandwidth.

ok, I used wireshark to measure the amount of bandwidth taken by one
sync when there are no new commits (which is just a series of no-op
git fetches), it comes out to 669838 bytes. calculating based on the
hosting provider's published rate of 5 GBP / TB bandwidth (which is
overcounting since afaict they count the max of upload and download
bandwidth rather than the sum):
(669838*byte) * 1/(15*min) * (60*min/hr) * (24*hr/day) *
(365.2425*day/yr) * (5*gbp)/(1e12*byte) gives:
0.117*gbp/yr (rounded to 3 decimals)

this is a trivial enough amount that I can pay you 10x that per year
if you like...

the total amount of time used per sync was 55s

can I set it to at least once per hour since this is the exact same
git sync that runs our CI and people depend on CI being somewhat
timely for their work, I know at least ghostmansd and I often look at
the CI right after we push stuff.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the libre-soc-bugs mailing list