![]() ![]() ![]() |
|
RalphFromSnap: Hello,
we are discussing with Chorus (as it is isolated to Chorus only UFB sites) and hope to have this resolved shortly. but just to be clear we certainly regard this as an open fault/issue and its top priority to get resolved quickly. (it has taken longer than we had hoped to resolve, we really do want to get this sorted ASAP!)
Thanks,
Snap
SneakerPimps: Noodles - can you try http://mirrors.gigenet.com/ubuntu/quantal/ubuntu-12.10-desktop-i386.iso
For me:
(Snap UFB)
1 Thread - ~130KB/s
5 Threads - ~650KB/s
(Xtra DSL)
1 Thread - ~300KB/s
5 Threads - ~1.5MB/s
Noodles:SneakerPimps: Noodles - can you try http://mirrors.gigenet.com/ubuntu/quantal/ubuntu-12.10-desktop-i386.iso
For me:
(Snap UFB)
1 Thread - ~130KB/s
5 Threads - ~650KB/s
(Xtra DSL)
1 Thread - ~300KB/s
5 Threads - ~1.5MB/s
Snap UFB 100/50:
1 Thread - ~266KB/s
5 Threads - ~1147KB/s
Snap ADSL:
1 Thread - ~360KB/s
5 Threads - ~851KB/s
Hmm...
Bodisaffa: The fact you are getting the speeds you are getting on SNAP VDSL only highlights how broken SNAP's UFB is.
It's just incomprehensible that SNAP's international download speeds on UFB can be slower by a long way than ADSL, VDSL and in my case even mobile data.
I'm awaiting SNAP's response hoping they can sort this out.
mattgreen:Bodisaffa: The fact you are getting the speeds you are getting on SNAP VDSL only highlights how broken SNAP's UFB is.
It's just incomprehensible that SNAP's international download speeds on UFB can be slower by a long way than ADSL, VDSL and in my case even mobile data.
I'm awaiting SNAP's response hoping they can sort this out.
Not sure why you think it's Snap at fault here. Orcon UFB customers are also complaining about performance when their ADSL customers aren't.
mercutio:mattgreen:Bodisaffa: The fact you are getting the speeds you are getting on SNAP VDSL only highlights how broken SNAP's UFB is.
It's just incomprehensible that SNAP's international download speeds on UFB can be slower by a long way than ADSL, VDSL and in my case even mobile data.
I'm awaiting SNAP's response hoping they can sort this out.
Not sure why you think it's Snap at fault here. Orcon UFB customers are also complaining about performance when their ADSL customers aren't.
It's most likely an issue with not rate limiting users properly, and hitting Chorus's rate limits. which Snap should be able to fix by implementing QoS/AQM on their BRAS servers. That's sounding more technical than I'd hoped to sound.
But basically, it's like if too many packets are sent, then data will just be dropped, and instead you want it to be queued for a period - ie there may be 1/1000th of a second of buffering, when you want 10/1000ths a second of buffering. The way TCP/IP transfers work speed keeps ramping up until there is packet loss, but a see saw pattern of spiky and erratic transfer speeds can happen when the line is much faster than the limit.
Unfortunately a quick google serach isn't hilighting anything to illustrate such.
mattgreen:You need to think of it in terms of the medium being available or not available for transmit/receive in each split second.
The minimum handover for UFB at a POI is 1Gb though right? One would assume Snap would have buckets of bandwidth relative to customers in the catchment areas so shouldn't be a problem.
|
![]() ![]() ![]() |