Your datapipe will be limited in bandwidth. You WILL have to slice pieces off it for your users. For what it's worth, all ISPs here (south-eastern Europe) word it like this:
- Xup/Ydown MBps for connections within the country (i.e. ones for which we can guarantee the infrastructure)
- X2up/Y2down MBps for connections farther away (i.e. subject to more variables)
- If you exceed N simultaneous TCP sessions, we reserve the right to drop some of them when the network is under load.
Basically, see how much you're getting from your provider and in how many pieces you can slice it and how much it will cost to buy fatter pipes when you have more users.
Give mid-bounds for speed - tell the customer their speed is usually this, but might be less under very heavy load (rare) or more when the network has spare capacity. But do sell slower/faster connections. This way you can sell better connections more expensively to people with more money.
Never put limits on how much data a user can down/upload. That is limited by their speed.
Make sure your equipment won't die if someone really does start an http server and posts the link on /. with "an experimental raspberrypi http server that can serve 100k simultaneous connections; do your worst :)".
Basically, I want my connection to have low latency, 99.999% reliability and you want me to pay as much money as I'm comfortable.
- Xup/Ydown MBps for connections within the country (i.e. ones for which we can guarantee the infrastructure)
- X2up/Y2down MBps for connections farther away (i.e. subject to more variables)
- If you exceed N simultaneous TCP sessions, we reserve the right to drop some of them when the network is under load.
Basically, see how much you're getting from your provider and in how many pieces you can slice it and how much it will cost to buy fatter pipes when you have more users.
Give mid-bounds for speed - tell the customer their speed is usually this, but might be less under very heavy load (rare) or more when the network has spare capacity. But do sell slower/faster connections. This way you can sell better connections more expensively to people with more money.
Never put limits on how much data a user can down/upload. That is limited by their speed.
Make sure your equipment won't die if someone really does start an http server and posts the link on /. with "an experimental raspberrypi http server that can serve 100k simultaneous connections; do your worst :)".
Basically, I want my connection to have low latency, 99.999% reliability and you want me to pay as much money as I'm comfortable.