Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Developers - How much Bandwidth is reasonable?

msattmsatt Member, Host Rep

Working on some great new features for FOSSVPS front end.
But before I release anything I would like your opinion.
FOSSVPS is for developers of Open Source Software. It is not for 'hosting'. So what would be a reasonable amount of data transfer in / out that should be allocated per client per month. Bear in mind that projects would need down / uploading.
Genuine feedback appreciated <3

Comments

  • rpqurpqu Member

    10GB

    Thanked by 2msatt foxbinner
  • For most dev/API workloads bandwidth is rarely the bottleneck — a couple TB/month covers a lot unless you're serving media or large downloads. I'd worry more about RAM and disk I/O. If you're running something chatty (lots of small requests) connection handling matters more than raw transfer. What kind of app is it?

    Thanked by 1msatt
  • conceptconcept Member

    yea 2-3TB is the minimum.

    Thanked by 1msatt
  • Neat321Neat321 Member

    Maybe 1 TB in+out if someone wants to serve a project packages repository, for example.

    Thanked by 1msatt
  • yoursunnyyoursunny Member, IPv6 Advocate

    We checked our devbox.
    We used just over 2GB in a week.

    ubuntu@d-ndndev:~$ uptime
     23:17:40 up 8 days,  8:28,  7 users,  load average: 0.10, 0.20, 0.21
    ubuntu@d-ndndev:~$ ip -s -h link show eth0
    2: eth0@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
        link/ether 2a:75:f2:ee:32:42 brd ff:ff:ff:ff:ff:ff link-netnsid 0
        RX:  bytes packets errors dropped  missed   mcast           
             1.53G   2.72M      0       0       0       0 
        TX:  bytes packets errors dropped carrier collsns           
              622M   2.08M      0       0       0       0
    
    Thanked by 2xdb msatt
  • msattmsatt Member, Host Rep

    Thanks for the comments - my key point is 'It is not for 'hosting'.
    So TBs of data is out of the equation. On the OGF the comments were that 50GB should be enough because you are pushing and pulling your code.
    My feeling was a 'soft' limit of 40GB with a bimonthly 20GB boost. So average is 50GB per client. This then gives me a max b/w for the node so our generous donors - @Alexhost, @Hosteroid and @st-hosting know what to expect. It is unfair to expect unlimited bandwidth with no limitations.
    I am very open to further discussion.

  • igcttigctt Member

    great, for most of git operations, it won’t consume much traffic though, even at very first maybe some large files.
    And for some specific reason , more traffic can be considered case by case.

    Thanked by 1msatt
  • woinokizwoinokiz Member
    edited June 13

    I never found high bandwidth critical for my projects , even with 100k+ WAU you can rarely cross 10TB/M

    Thanked by 1msatt
  • msattmsatt Member, Host Rep

    @igctt said:
    great, for most of git operations, it won’t consume much traffic though, even at very first maybe some large files.
    And for some specific reason , more traffic can be considered case by case.

    Absolutely - if a developer needs more b/w they only have to ask.
    Also if the B/W is exceeded the NIC will just be throttled to some low amount (to be decided but likely 50Mbps).

    Thanked by 1igctt
  • For development I would say near 25GB a month is enough. And I would recommend throttling to less then 50Mbps after the cap, 10Mbps should be good.

    Thanked by 1msatt
  • Neat321Neat321 Member

    @msatt said:
    Thanks for the comments - my key point is 'It is not for 'hosting'.
    So TBs of data is out of the equation. On the OGF the comments were that 50GB should be enough because you are pushing and pulling your code.
    My feeling was a 'soft' limit of 40GB with a bimonthly 20GB boost. So average is 50GB per client. This then gives me a max b/w for the node so our generous donors - @Alexhost, @Hosteroid and @st-hosting know what to expect. It is unfair to expect unlimited bandwidth with no limitations.
    I am very open to further discussion.

    Since it's not for hosting, 30–40 GB is enough for Git operations, etc.

    Thanked by 1msatt
  • I would say 3-4 TB to sit comfortably. Some developers like to deal with LFS for which high bandwidth requirement is a must.

  • msattmsatt Member, Host Rep

    Thanks for the feedback :)
    I have built the automation to allow 50GB with a warning at 40GB. If the previous month did not exceed 50GB, a 'boost' of 20GB happens. If the limit (50 or 70GB) is reached then the B/W is limited.
    @buggedout - I think 10Mbps is like a real slap, so I have dropped to 50Mbps until the monthly reset happens.
    @Protocol903 - LFS is likely too big a project for FOSSVPS and the B/W is certainly too much. But thanks for flagging this as I had not considered it. If however a developer would like a bigger local disk I am happy to oblige, providing this is for genuine development.

    The purpose of this 'filtering' is that in the past there has been abuse mainly from NodeSeek users where they say one thing and do another e.g. proxies & vpn. I have absolutely no intention of accessing the VPS to 'see' what they are doing so want to maintain this passive approach.

    So what do developers 'feel' about this solution?

  • rpqurpqu Member
    edited June 14

    @msatt said:
    The purpose of this 'filtering' is that in the past there has been abuse mainly from NodeSeek users where they say one thing and do another e.g. proxies & vpn. I have absolutely no intention of accessing the VPS to 'see' what they are doing so want to maintain this passive approach.

    So what do developers 'feel' about this solution?

    I think the only acceptable high network usage as proxy/vpn in FOSSVPS, if they're active contributor to a popular/new (but gaining momentum) proxy-vpn repository 😅😅😅. Even then, it has to be capped, 1-2TB at max

    Thanked by 1msatt
  • buggedoutbuggedout Member

    @msatt said:
    @buggedout - I think 10Mbps is like a real slap, so I have dropped to 50Mbps until the monthly reset happens.

    I was thinking that 50Mbps is still decent for exploitors looking to hammer with some vpn or similar thing. But yeah for real devs it might be too restrictive !!

    Thanked by 1msatt
Sign In or Register to comment.