![]() Registered Member ![]()
|
Hi there,
I find that capping doesn't work for me. I am on a relatively slow DSL line (768kbit/s down, 128kbit/s up) and rely on the capping feature to preserve some bandwidth for other users. Symptoms: capping does not work as intended. Particularly the upload speed tends to max out which slows down the whole internet connection for everybody on the LAN. The symptoms vary - it is not 100% deterministic. Sometimes the upload speed maxes out no matter which cap I have specified. Sometimes it appears the upload speed simply exceeds the cap value by a fixed amount of 4kByte/s or so, which is a significant part of the available bandwidth. Interestingly, the KTorrent application reports an upload speed consistent with the cap. It is the eth0 interface speed (and also the interface speed reported by the DSL router) that is significantly higher. When I pause KTorrent, the speed reported by KTorrent drops to 0, whereas the interfaces report 2kByte/s (plus/minus a few) in both directions. When I kill KTorrent, the interface speeds drop to 0. I am very certain this behaviour is new. Unfortunately I had quite a few changes recently so I cannot pinpoint the exact trigger:
Btw, I have implemented the heavily reduced connection settings recommended in the FAQ on the Wiki, but that had no effect on the problem at hand. Since I have not found any other reports of this nature on the web, maybe I am doing something wrong? Martin |
![]() Moderator ![]()
|
The upload and download cap only cap the actual data transfers. It does not take into account, protocol overhead (TCP and IP).
|
![]() Registered Member ![]()
|
I hear what you're saying, but I am 100% certain I did not experience this type of bandwidth saturation before. Any overhead used to be small compared to the actual data transfer. Martin |
Registered users: Bing [Bot], blue_bullet, Google [Bot], rockscient, Yahoo [Bot]