From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [POLL] [VOTE] code.ffmpeg.org
Date: Sun, 13 Jul 2025 18:07:12 +0200
Message-ID: <5a8b9687-220f-4db1-bdb3-8a5f96e25809@rothenpieler.org> (raw)
In-Reply-To: <20250713155722.GE29660@pb2>
On 7/13/2025 5:57 PM, Michael Niedermayer wrote:
> Hi
>
> On Sun, Jul 13, 2025 at 01:58:44PM +0200, Timo Rothenpieler wrote:
> [...]
>
>> Just want to note that hosting Gitlab is quite a bit more expensive than
>> Forgejo, for which I'm currently just paying out of pocket.
>> So for an official Gitlab test setup, I'd occasionally forward accumulated
>> bills for refund by SPI.
>
> Can you elaborate on the source of this additional cost ?
It's written in Ruby, which is not exactly fast or light on resources.
The recommended minimum instance Gitlab defines is one with 16GB RAM and
8 cores.
Gitlab also does not officially support running on aarch64, though it
does supposedly work, you'd be on your own supporting that setup.
So while a Forgejo instance suitable for our expected usage can run on
an CAX21 instance (4 CPUs, 8GB RAM, aarch64) which costs 7,13€ a month,
the Gitlab minimum specs demand a CX42 or CPX41 instance for 18,92€ or
29,39€ a month (both are 8CPU, 16GB RAM, the more expensive "P" one
being faster AMD CPUs, the non P one Intel).
The Intel CPUs are likely fine, performance wise, but it's still almost
triple the cost at a minimum.
If Gitlab could run on aarch64 the respective CAX31 instance would cost
only 14,27€ a month.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-07-13 16:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 11:43 Michael Niedermayer
2025-07-13 11:49 ` Kieran Kunhya via ffmpeg-devel
2025-07-13 11:58 ` Timo Rothenpieler
2025-07-13 15:57 ` Michael Niedermayer
2025-07-13 16:07 ` Timo Rothenpieler [this message]
2025-07-13 16:15 ` Timo Rothenpieler
2025-07-13 18:51 ` Kieran Kunhya via ffmpeg-devel
2025-07-13 19:03 ` Yalda
2025-07-13 14:38 ` Rémi Denis-Courmont
2025-07-13 15:56 ` Jacob Lifshay
2025-07-13 15:58 ` Timo Rothenpieler
2025-07-13 17:35 ` Michael Niedermayer
2025-07-13 18:04 ` Ronald S. Bultje
2025-07-13 19:47 ` Timo Rothenpieler
2025-07-13 21:47 ` Michael Niedermayer
2025-07-13 22:07 ` Kieran Kunhya via ffmpeg-devel
2025-07-13 21:55 ` Philip Langdale via ffmpeg-devel
2025-07-13 22:04 ` Timo Rothenpieler
2025-07-13 22:22 ` Marvin Scholz
2025-07-14 2:43 ` Zhao Zhili
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a8b9687-220f-4db1-bdb3-8a5f96e25809@rothenpieler.org \
--to=timo@rothenpieler.org \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git