Afrihost Capped vs Uncapped QoS

[MrG]

I have noticed two different scenarios running the two accounts and I would like to know why it is setup like this. The behavior below seems that there is ISP side QoS on uncapped accounts that do not exist on capped accounts?

ADSL: 2Mbps Line - Single User

Scenario 1: Free 1GB Capped Account

Google ChromeCast: Streaming YouTube
Laptop: Browsing web pages.

Result: Web pages load as quickly as one would expect in given scenario, ChromeCast adjusts video quality up and down now and again in order to avoid buffering.

Scenario 2: Home Uncapped Account

Google ChromeCast: Streaming YouTube
Laptop: Browsing web pages.

Result: Web pages often time-out or load extremely slowly, ChromeCast stays on maximum video quality and does not buffer.

Secondary test: When ChromCast stops playing browsing returns to normal.

Tertiary test: Having the Chromecast play on the uncapped account (on router) and the laptop create it's own PPoE connection on the standard capped account, it acts the same way as Scenario 1.

 

[catman37]

Should this not rather be Afrihost Unshaped Capped versus Afrihost Shaped Capped versus Aftibost Uncapped?

 

[MrG]

Should this not rather be Afrihost Unshaped Capped versus Afrihost Shaped Capped versus Aftibost Uncapped?

Fixed for clarity.

How do you propose the shaping on the products are affecting this? I would not have thought that shaping would deprioritize HTTP traffic.

 

[ranger]

Fixed for clarity.

How do you propose the shaping on the products are affecting this? I would not have thought that shaping would deprioritize HTTP traffic.

Not all HTTP traffic is necessarily equal.

It is easy to differentiate youtube or similar from web browsing on any DPI platform.

I wouldn"t do it this way, but it could be that Afrihost applies per-subscriber shaping with protocol(application)-based prioritisation *without* ensuring there isn't starvation of the lower-priority traffic. This would lead to the behaviour you are seeing.

 

[MrG]

Not all HTTP traffic is necessarily equal.

It is easy to differentiate youtube or similar from web browsing on any DPI platform.

I wouldn"t do it this way, but it could be that Afrihost applies per-subscriber shaping with protocol(application)-based prioritisation *without* ensuring there isn't starvation of the lower-priority traffic. This would lead to the behaviour you are seeing.

Interesting.

Even with that error of starvation, I would have thought it would be the YouTube traffic that suffers rather than the web browsing. Clearly Afrihost is not prioritizing web browsing above that of YouTube traffic on their Home Uncapped accounts.