Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Comment Re:Data caps are inevitable for shared media (Score 1) 198

But we are not discussing a "typical" case here. What happens, when in a group of 64, 3 or 4 users decide to download all day long? How will this affect the rest of the group?

The main difference is that the "network" is built from routers which (if properly configured) can distribute the bandwidth fairly among all connections/users/ip addresses in the event of a congested link. You can't have fair bandwidth allocation in a "shouting chamber" type medias, unless the ISP has control over the router on the premises.

You mention a very interesting point! fairness guarantees in a shared medium vs fairness in a switched network. I agree that they differ, and that shared-medium systems are much more prone to abuse.

In a shared-medium system with distributed medium access control, such as a Wi-Fi network (using the CSMA/CA MAC mechanism), users compete to send data, and the system may be abused by a single user sending too much data. In fact, under high pressure the performance degrades for all the users.

However, in systems controlled by an ISP, the medium access control mechanism is typically arbitrated by the ISP equipment, instead of using contention-based mechanisms. We can consider download and upload sepparately. The download channel is always controlled by the ISP, since the data comes from its own device (the OLT in GPON, the In the case of GPON, the CMTS in DOCSIS, the satellite and the rest of the network in Starlink) so they can always modulate how much data is received by each user using queueing policies. I agree that this is not perfect, since users are typically considered by QoS classes (and not individually), but there are some QoS mechanisms in place. In the upload channel, to avoid the abuse and guarantee fairness and/or QoS, the ISP equipment typically controls the allocation of resources for each user. For example, in GPON the OLT assigns bursts of data (time slots within the upstream frame) to each ONU client, based on the occupancy of their queues. In DOCSIS, the CMTS (the headend device from the ISP) periodically sends MAP messages, with minislot allocations based on previous requests by the cable modems. There are no public details of the MAC mechanism employed in Starlink (that I am aware of), but it is very likely that the satellite controls the allocation of resources per user both in the downlink (obviously) and the uplink, preventing abuse by a single user.

The problem in these systems with centralized arbitration is not so much fairness, which can be somewhat controlled by the arbiter from the ISP at the MAC layer. By contrast, the problem is typically capacity, since the capacity of the (typically, wireless) channel is often very limited and the channel highly oversubscribed. This is why data caps unincentive the use of the network, reducing the offered traffic load and improving observed performance by all users. By contrast, capacity issues in other systems (such as GPON) typically occur at the backbone, which can be much more easily upgraded.

Comment Re:Data caps are inevitable for shared media (Score 5, Informative) 198

You are making two mistakes with your argument.

First, you are presenting some examples in which your argument does not apply. Consider GPON (G.984) as an example: Nominal download speed is 2.48 Gbps, shared by up to 64 users, and ISPs often sell up to 1 Gbps per user. Thus, each user may be allocated, in theory, a sustained 2.48x1/64=3.87%, or 38.75 Mbps, regarless of their maximum "paid-for" speed. However, the typical situation is very far from these numbers of the worst case: The number of users per fiber is typically lower than 64; not all of them are downloading simultaneously; and even in a typical use case (web, HD streaming) 38 Mbps is more than enough.

Additionally, in GPON there are many fibers per OLT (the headend device at the provider's premises), so they can serve more users. Same applies to DOCSIS. The problem for starlink is that there is only one satellite (not one satellite with many fibers) and the number of users in an area can be huge, way larger than the 64 limit in GPON.

Your second mistake is that you exclusively focus on the last mile, whereas any network is always shared among many users. Even if the last mile is private (e.g. a dedicated Ethernet wire), after the headend router from the ISP the backbone is shared by many, many users. Depending on the oversubscription factor, the congestion point may occur in the last mile or the backbone after the headend. In Starlink the bottleneck will clearly be in the last-mile (or maybe "last 250-miles"?), but this does not occur in all cases (in GPON it will be probably in the backbone).

Comment Sounds like (Score 5, Insightful) 45

Arm is killing their own business model. If designers (such as Qualcomm, with an architectural license) find that combining their own cores with other IP is very complicated, they might start considering seriously the migration to a different ISA. And when they move to RISC-V, they will not come back to ARM.

Slashdot Top Deals

UNIX is hot. It's more than hot. It's steaming. It's quicksilver lightning with a laserbeam kicker. -- Michael Jay Tucker

Working...