Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance impact of PPP on cellular networks #13

Open
Kevsy opened this issue Apr 30, 2021 · 2 comments
Open

Performance impact of PPP on cellular networks #13

Kevsy opened this issue Apr 30, 2021 · 2 comments

Comments

@Kevsy
Copy link

Kevsy commented Apr 30, 2021

I have a few concerns/questions regarding default (user opt-out) use of PPP on a cellular network:

  • the user experience benefit of faster browsing seems plausible on an uncongested network with good radio conditions to that user. But should either congestion or interference occur, then the prefetch content is then in competition with explicitly requested content for scarce radio resources. The scheduler has no way of knowing which content the user explicitly requested vs. that which they may choose to navigate to: meaning some users will be waiting for their content because others are receiving their ‘on the off chance’ prefetch.
  • I suspect the problem above is exacerbated by any frustrated users hitting ‘refresh’, triggering both duplicate content requests and prefetch requests.
  • I’d be interested to see metrics for how prefetch affects traffic volume and bursts to the scheduler packet queues.

Many thanks!

@chris-box
Copy link

The issue is more general than cellular. Congestion can affect all networks, and is not restricted to the last mile. But in practice the area where this will be most visible is in cellular networks because utilisation can be routinely high and capacity expansion at the edge is expensive.

Some explanation of the scheduling issue may be useful. In LTE, a cell's scheduler often has multiple phones it needs to deliver queued downlink packets to. Every millisecond it needs to decide which packets to send in the next millisecond, by dedicating resource blocks to them. This is influenced by radio conditions but also other factors, such as needing to be fair to all users, maximising overall throughput, etc.

Kevin is highlighting a scheduler that has downlink packets for two phones, one of which is waiting for a response to its user-initiated query and the other is expecting some prefetch data. In current networks the scheduler will have no notion that these are of different importance, and it will treat them the same. The result is that "some users will be waiting for their content because others are receiving their ‘on the off chance’ prefetch".

Are there solutions to this? I think there are. If PPP packets were marked in some way, e.g. by the IP address of the prefetch proxy being known to the cellular network, or by DSCP mark, then the cellular network could apply QoS Class Indicator (QCI) to reflect its lower priority status. The scheduler can then take that into consideration. If implemented well, all users should obtain the speed benefits of prefetch without the speed loss of increased congestion.

@Kevsy
Copy link
Author

Kevsy commented May 20, 2021

I think operators need to be aware of the potential increase in connection-mapping/connection-state at the stateful NAT. So figures summarising the increase in outgoing connection requests would also be appreciated, in case scaling is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants