Sid Elbow wrote:
> On 2/27/2012 4:57 PM, Patok wrote:
>> Sid Elbow wrote:
>>>
>>> When I set a global upload speed limit in Vuze, it displays, in square
>>> brackets, on the bottom line correctly but consistently shows actual
>>> upload speeds that are far greater - it seems to be around 50% more or
>>> perhaps higher.
>>>
>>> For instance, right now I have it set for 60 kB/s max but it's happily
>>> chugging along at 80 - 90 kB/s.
>>>
>>> It's worked fine for years
>>
>> Azureus/Vize has a hardcoded lower limit of 300 KB/s, in the source
>> code. When you set the limit manually or through Auto Speed - doesn't
>> matter which - it never drops below 300.
>
> 300 KB/s ??? ..... it would be nice. My service is limited to 700 Kb/s
> upload speed - say 70 KB/s. Because of downloading overhead, using all
> of this upload capacity would kill the downloads - see Azureus/Vuze wiki
> (
http://wiki.vuze.com/w/Auto_Speed) so you can only use about 80% of it.
> Say 55 KB/s.
[snipped some true stuff]
> Incidentally, nothing under that Azureus setting indicates there is any
> lower limit to the upload speed nor is there anything anywhere in the
> Vuze wiki. I don't for one minute believe there is such a lower limit
> (there's no logical reason for it for one thing). That it would be 300
> KB/s is, in any case, not credible.
It is not credible, but for a different reason - I misremembered. :(
There *are* hardcoded lower limits for both download and upload, but 300
is the limit for download, while the limit for upload is 10. So you are
correct - your upload speed should be able to go down to 10 KB/s, while
your download speed should be limited to no less than 300. What I now
recall was bugging me at the time was when visiting my brother who had
DSL, the *download* speed being 300 KB/s saturated his line, so I was
not able to use it there. And you're right, it is not mentioned anywhere
in the docs - that's what upset me at the time and I wanted to contact them.
Here are the relevant sections from AzureusCoreImpl.java from the source
for version 4.2.0.8 (the one I downloaded at the time to look for clues):
speed_manager =
SpeedManagerFactory.createSpeedManager(
this,
new SpeedManagerAdapter()
{
private final int UPLOAD_SPEED_ADJUST_MIN_KB_SEC = 10;
private final int DOWNLOAD_SPEED_ADJUST_MIN_KB_SEC = 300;
private boolean setting_limits;
................
public void
setCurrentUploadLimit(
int bytes_per_second )
{
if ( bytes_per_second != getCurrentUploadLimit()){
String key = TransferSpeedValidator.getActiveUploadParameter(
global_manager );
int k_per_second;
if ( bytes_per_second == Integer.MAX_VALUE ){
k_per_second = 0;
}else{
k_per_second = (bytes_per_second+1023)/1024;
}
if ( k_per_second > 0 ){
k_per_second = Math.max( k_per_second,
UPLOAD_SPEED_ADJUST_MIN_KB_SEC );
}
COConfigurationManager.setParameter( key, k_per_second );
}
}
........................
public void
setCurrentDownloadLimit(
int bytes_per_second )
{
if ( bytes_per_second == Integer.MAX_VALUE ){
bytes_per_second = 0;
}
if ( bytes_per_second > 0 ){
bytes_per_second = Math.max( bytes_per_second,
DOWNLOAD_SPEED_ADJUST_MIN_KB_SEC*1024 );
}
TransferSpeedValidator.setGlobalDownloadRateLimitBytesPerSecond(
bytes_per_second );
}
>> But since then I have internet speeds in the range of MB/s, so I don't
>> bother.
>
> If you're talking upload speeds "in the range of MB/s" you are very
> fortunate. But 99 % of people don't even come close.
I guess so. Sorry. 25 Mbit/s up and down home, gigabit at work.
>> However, I am really surprised by what you write - that it has ever
>> worked. Are you sure about that?
>
> ... er .... yes. I don't have that good an imagination.
:)
> Unless the SpeedSheduler you mention
>> used to work before, and broke in recent releases?
>
> Haven't updated it since I got it. AFAIK there are no later releases.
I meant the Azu/Vuze releases. Are you updating it?
> (I've never used it,
>> I don't know what it is).
>
> No kidding.
Indeed. :) Where did you get it? I don't think it is one of the
built-in automatic ones that self-install.
What is bugging me in the current version (starting with 4.7) is they
removed the option for opening the Options tab on startup (this is in
the classic Azureus UI, Advanced mode). Before, there was the option of
doing that, and on startup I had the 3 tabs open - Torrents, Statistics,
and Options. Now it is no longer an option to do that, and it starts
with Torrents and Statistics only. I have to open Options manually. Oh,
well.