Sign up with GoogleWhy can't the speeds stay at 32KB/s+ and what the hell is up with the upload speeds!?
-
Ask a question and get free supportUnlock new privileges and see hidden discussionsWin prizes and earn reputation
-
Question of the day ~ How often do you braai?
-
Afristay giveaway.Win a 2-night stay for two people at an establishment of your choice with R1,000 in spending money. Enter here.
DigiChilli January Status and feedback
- Thread starter CambodiaDave
- Start date
-
- Tags
- digichilli
Why can't the speeds stay at 32KB/s+ and what the hell is up with the upload speeds!?
Daywalker29
Well-Known Member
- Joined
- Jan 11, 2010
- Messages
- 109
Im not sure what is going on with there speeds, and some how i think DC dont know as well, i got a few email from Andre today and this was what he said to me last.
Hi
Constructive feedback. We are looking into this now. We are busy building a cache server that will free up ALLOT of international bandwidth which will allow us to burst again to good speeds.
I am busy looking into why we are not getting the best of speeds and will feedback soonest.
Regards
Andre
Hi
Constructive feedback. We are looking into this now. We are busy building a cache server that will free up ALLOT of international bandwidth which will allow us to burst again to good speeds.
I am busy looking into why we are not getting the best of speeds and will feedback soonest.
Regards
Andre
Last edited:
angelblaze
Well-Known Member
- Joined
- Dec 20, 2007
- Messages
- 108
ooh a cache server. yes please!
Its quite interesting that they haven't turned on the cache server yet. Once completed it should improve capacity by about 20%.
The local NS will probably also save another 20%(could be more) if users start migrating to it.
So thing are looking up.
The local NS will probably also save another 20%(could be more) if users start migrating to it.
So thing are looking up.
Daywalker29
Well-Known Member
- Joined
- Jan 11, 2010
- Messages
- 109
Yip this is true but like myself and others i hope im still sitting with shocking speeds, at this moment upload is 1.2KB/s and download is 0.2KB/s But at least i can still browse sort of
angelblaze
Well-Known Member
- Joined
- Dec 20, 2007
- Messages
- 108
Hey DC, post the cache server address/port here and we will beta test it for you before you deploy it for everyone. 
sallyspencer
Senior Member
- Joined
- May 28, 2007
- Messages
- 695
Mine has all gone slowly downhill....http download speeds have gone from 20 to 3 and that is where they are staying now.....browsing is torture.....:twisted::wtf:
Summary of application test results
Download speed 15 Kbps
Upload speed 54 Kbps
Quality of service 8 %
Round trip time (min) 352 ms
Max delay 3422 ms
Bandwidth 47 Kbps
Timer accuracy 1 ms
Analysis of application test results
1. Timer clock resolution recorded for this test is accurate to 1ms. This means that the test results will be very precise especially the service quality. MyConnectionPC intentionally tests the timer to be sure that the stop-watch used to measure the data is capable of being accurate which is important on a timesharing PC platform. In particular a 1ms timer allows MyConnectionPC to monitor the TCP stack and the packet flow accurately. This provides data on congestion as well as regulation delays.
2. Download speed 15Kbps recorded is materially less than the bandwidth capacity 47Kbps calculated for the connection. This means that the latency created by the distance may be causing the connection to degrade. This is natural and cannot change but you should review the Trip Time analysis below to be sure that there are not other quality issues affecting data throughput such as packet loss caused by congestion etc. If the Max bandwidth reported is not correct then this implies that there may be a data flow quality problem that is causing the capacity to be miscalculated. You can do a capacity test to verify this however the problem will still exist. If QoS is low this will be further confirmation.
3. Round trip time 352ms recorded for this test is close to 11108ms needed to support 47Kbps capacity calculated for the connection. This means that time taken for the data packets to travel the distance is fast enough to ensure your PC is not idle waiting for data to arrive. This is because the sending server is able to send more data before your PC has finished processing the data already sent. The faster your connection the less likely this will happen and delays will occur. For most common internet needs speeds greater than 10Mbps will seldom be achieved because the latency of the connection will dictate slower throughput speeds.
4. QoS measure of 8% recorded for this test is very poor indicating severe problems with the data flow going fast-slow-fast-slow during the test. MyConnectionPC measures the data flow as well as the data speed to detect congestion or regulation patterns. If the data flow is not consistent then it will result in a low QoS reading for the test. The most likely cause for this problem is contention caused by congestion. If the speed graph is very erratic i.e. not uniform then this indicates congestion, uniform indicates by design i.e.regulation. One of the causes for a low QoS is a high Max Delay and you should review the Max Delay for this test.
5. Max delay of 3422ms was recorded which is very high and indicate data loss problems with the delay being caused by recovery. This will almost certainly cause the QoS to drop. Because MyConnectionPC measures the data flow as well as the data speed it can detect traffic delays. This metric reports the largest delay recorded for the test. The most likely cause for a high max delay value is packet loss because packet loss causes recovery actions to take place. However high latency connections will always cause TCP idle delays which will show in the graph as very regular and repeated delays all about the same value. This is a natural delay that cannot be avoided. The Trip Time value reports the route latency.
6. Bandwidth measure of 47Kbps recorded for this test reports the max capacity for the connection being tested not the speed of test. MyConnectionPC analyzes the packet arrival rates specifically to calculate the capacity (not application) speed of the connection. The capacity speed is the maximum capability of the connection. Knowing the capacity of the pipe during an application test allows MyConnectionPC to validate if the Trip Time is causing a problem for the application test or not and reports it accordingly. If the max bandwidth reported is not correct for the connection then this implies that there may be a data flow quality problem that is affecting the test and causing the capacity to be miscalculated. You can do an actual capacity test to verify this however the problem will still exist. If QoS is low this will be further confirmation.
:twisted::wtf:Summary of application test results
Download speed 15 Kbps
Upload speed 54 Kbps
Quality of service 8 %
Round trip time (min) 352 ms
Max delay 3422 ms
Bandwidth 47 Kbps
Timer accuracy 1 ms
Analysis of application test results
1. Timer clock resolution recorded for this test is accurate to 1ms. This means that the test results will be very precise especially the service quality. MyConnectionPC intentionally tests the timer to be sure that the stop-watch used to measure the data is capable of being accurate which is important on a timesharing PC platform. In particular a 1ms timer allows MyConnectionPC to monitor the TCP stack and the packet flow accurately. This provides data on congestion as well as regulation delays.
2. Download speed 15Kbps recorded is materially less than the bandwidth capacity 47Kbps calculated for the connection. This means that the latency created by the distance may be causing the connection to degrade. This is natural and cannot change but you should review the Trip Time analysis below to be sure that there are not other quality issues affecting data throughput such as packet loss caused by congestion etc. If the Max bandwidth reported is not correct then this implies that there may be a data flow quality problem that is causing the capacity to be miscalculated. You can do a capacity test to verify this however the problem will still exist. If QoS is low this will be further confirmation.
3. Round trip time 352ms recorded for this test is close to 11108ms needed to support 47Kbps capacity calculated for the connection. This means that time taken for the data packets to travel the distance is fast enough to ensure your PC is not idle waiting for data to arrive. This is because the sending server is able to send more data before your PC has finished processing the data already sent. The faster your connection the less likely this will happen and delays will occur. For most common internet needs speeds greater than 10Mbps will seldom be achieved because the latency of the connection will dictate slower throughput speeds.
4. QoS measure of 8% recorded for this test is very poor indicating severe problems with the data flow going fast-slow-fast-slow during the test. MyConnectionPC measures the data flow as well as the data speed to detect congestion or regulation patterns. If the data flow is not consistent then it will result in a low QoS reading for the test. The most likely cause for this problem is contention caused by congestion. If the speed graph is very erratic i.e. not uniform then this indicates congestion, uniform indicates by design i.e.regulation. One of the causes for a low QoS is a high Max Delay and you should review the Max Delay for this test.
5. Max delay of 3422ms was recorded which is very high and indicate data loss problems with the delay being caused by recovery. This will almost certainly cause the QoS to drop. Because MyConnectionPC measures the data flow as well as the data speed it can detect traffic delays. This metric reports the largest delay recorded for the test. The most likely cause for a high max delay value is packet loss because packet loss causes recovery actions to take place. However high latency connections will always cause TCP idle delays which will show in the graph as very regular and repeated delays all about the same value. This is a natural delay that cannot be avoided. The Trip Time value reports the route latency.
6. Bandwidth measure of 47Kbps recorded for this test reports the max capacity for the connection being tested not the speed of test. MyConnectionPC analyzes the packet arrival rates specifically to calculate the capacity (not application) speed of the connection. The capacity speed is the maximum capability of the connection. Knowing the capacity of the pipe during an application test allows MyConnectionPC to validate if the Trip Time is causing a problem for the application test or not and reports it accordingly. If the max bandwidth reported is not correct for the connection then this implies that there may be a data flow quality problem that is affecting the test and causing the capacity to be miscalculated. You can do an actual capacity test to verify this however the problem will still exist. If QoS is low this will be further confirmation.
Last edited:
Daywalker29
Well-Known Member
- Joined
- Jan 11, 2010
- Messages
- 109
I love getting up in the morning and seeing my downloads sitting at 0.2KB/s all night long....
+1
almost same...just abt 100Bytes here and there ....
What is wrong with DC....come on.....do something....
So let me get htis right, because of a bad network, Telkom, virtual pipe and now the News Servers we're getting the bad speeds coz of all that? Well that's all fixable but if we had updates at least we would complain so much. I can see if DC gets their NS up and running and get speeds to at least 30kB/s with burst very often, well then DC will be an awesome product Until then no updates and no speeds make for some very sad lonely days
Until then no updates and no speeds make for some very sad lonely days
Last edited:
sallyspencer
Senior Member
- Joined
- May 28, 2007
- Messages
- 695
Good morning all here is my test of the morning......
Summary of application test results
Download speed 15 Kbps
Upload speed 52 Kbps
Quality of service 8 %
Round trip time (min) 355 ms
Max delay 4372 ms
Bandwidth 58 Kbps
Timer accuracy 1 ms
Summary of application test results
Download speed 15 Kbps
Upload speed 52 Kbps
Quality of service 8 %
Round trip time (min) 355 ms
Max delay 4372 ms
Bandwidth 58 Kbps
Timer accuracy 1 ms
Prophet112
Well-Known Member
- Joined
- Dec 25, 2009
- Messages
- 298
Getting an average of 20KB/s on Rapidshare with the odd burst to 26-30KB/s which lasts a second.
Managed to get around a gig overnight.
Spicy 384
Managed to get around a gig overnight.
Spicy 384
Digichilli is a joke.... I had hopes and even after reading the negative comments here I still went ahead to try it out....
I am disgusted with the connection quality.... and the sheer throttling of the line is pathetic.
If Anyone is even considering going with Digichilli, DONT! you better off using a capped service cos u get about the same amount of data anyway.Except it works!
I am disgusted with the connection quality.... and the sheer throttling of the line is pathetic.
If Anyone is even considering going with Digichilli, DONT! you better off using a capped service cos u get about the same amount of data anyway.Except it works!
Willie Trombone
Honorary Master
- Joined
- Jul 18, 2008
- Messages
- 60,038
unfortunately it's too much of a yo yo for my liking... think I'm going back to my R29 per gig afrihost only.
Still no update from DigiChilli and the Speeds are insanely bad... After reading the latest comments and I totally agree... I don't see DigiChilli succeeding. It sucks! Would have liked a cheap and Burstable uncapped solution. But that ain't gonna happen with these guys! And what gets me most is no word from them, no heads up about network maintenance no NOTHING! AI! And all we ever if we ever hear from them is there are problems and they are attending to it...
And all we ever if we ever hear from them is there are problems and they are attending to it...
Last edited:
sallyspencer
Senior Member
- Joined
- May 28, 2007
- Messages
- 695
well my DC has just switched it's self off so had to change to my Telkom account.......:wtf::twisted:
well my DC has just switched it's self off so had to change to my Telkom account.......:wtf::twisted:
You're not alone! ><