Jump to content

Rate limits per torrent no longer work. Database problem?


KarlMarx999

Recommended Posts

Hi,

The rate limits that I apply per torrent no longer work. In the past I could reboot and restart and the rate limits would work. Not anymore.

I have tried updating to newer clients to no avail. I hate the latest interface, it wastes far too much desktop space and the file lists need smaller fonts and line spacing. I'm using 2.0.3 right now.

I'm very frustrated because this used to work until a few weeks ago. I need to restrict my incoming rates for some sites and my outgoing for others. This is a very big headache.

This problem exists for both old and new torrents.

I tried searching this site but found no answers.

I hope that some one out there has a fix for me.

Thanks

Link to comment
Share on other sites

@ DreadWingKnight - I don't care about that response (it is a NON response) The problem exists with the very latest!! If you check my original you will see that I did try the latest version but hated the interface that wastes so much desktop space. I was using 2.0.2 when the problem became a permanent one. I updated in steps all the way to the new piggy one and no change to the problem occurred.

@ Switeck - You missed the point. With no changes to the settings at all, one day it went out of control. Entirely out of control. I have seen the uTP actions in the past. I have tried the template response of turning off uTP to no avail. It is not a uTP issue. It is overflowing the Global settings at times too, but that is not my concern at this time (unlike all of the other posts that I saw). I need to be able to throttle per file.

This has all of the hallmarks of a database issue. It worked, then failed and now cannot seem to be fixed..I did try the other template response of removing the settings.dat.* files, also to zero effect.

I'm not a noob and I try to fix my own stuff, but this just has not revealed a solution. That is why I came here, to see if others might have better ideas.

Thank you for the time and I still hope to resolve this without a format reload type of thing.

Link to comment
Share on other sites

http://forum.utorrent.com/viewtopic.php?id=82840 <-- read the first post as to why the versions you have tried are not supported, among other reasons. If you don't want my "non-answer," have the decency to at least update to a current version of uTorrent first.

You also have not given enough information to troubleshoot, including wether or not you're getting local flagged peers on your torrents as well as WHAT settings you're using

Link to comment
Share on other sites

I've seen heavy CPU loads in other applications cause uTorrent to VASTLY overshoot its limits on its graph...but in reality uTorrent isn't uploading significantly if ANY faster than the limit. Often this shows up as "freezing" of the uTorrent gui as well and even mouse jerkiness. Firefox seems the most prone to do this when I have 100+ webpages open at once.

I've also seen uTorrent mistakenly identify a peer or seed as "local", which is NOT subject to the usual speed limits...UNLESS "Limit local peer bandwidth" is checked in Prefrences, BitTorrent

Are you seeing the blow-past-limit by >20% even when uTP is disabled?

...And can you rule out mis-identified (by uTorrent) "local" peers/seeds?

Link to comment
Share on other sites

@ Switeck - I thought about CPU overload, but the problem appears after a reboot with just uTorrent running. There are no local peers except me (about 12 machines). Only one PC runs uTorrent at a time. I have certainly seen the local peer uptick when more than one PC was working on downloading the same file. It is extreme, but not what is happening here. The sdpeed will go over 1500 when that happens.

@ DreadWingKnight

I never claimed to be nice. - OK, I'll spell it out. I USED 2.2! That is the version that wastes too much space. You can see very few files because of the spacing, etc. BTW, You have earned your tag line.

I updated to each and every version from 2.0.2, where the problem appeared, on through 2.0.3 and 2.0.4 along the way. The problem existed on each and every version. One of the sites that I support sent me a note not to use 2.0.4 and that if I did not change, that I would be banned. That is why it is on 2.0.3 now. If you are saying that only 2.0.4 and 2.2 are supported, then is an unhappy situation.

What settings mean the most for you? Why would that matter when it suddenly changed speeds with no setting changes on my part? I have seen this problem in the past, as I said, but a reboot took care of it those times. Again, no settings changes. I don't think that settings are the issue here.

Here is a picture:

limitsfail.jpg

I shot just a small section. I hope that this satisfies.

Link to comment
Share on other sites

One of the sites that I support sent me a note not to use 2.0.4 and that if I did not change, that I would be banned.
Did they give you a good reason for this? (One good enough to risk your system's security against hackers)
If you are saying that only 2.0.4 and 2.2 are supported, then is an unhappy situation.
That I am, and 2.0.4 is in its "End of support" phase. Once 2.2 is fully on the autoupdater, 2.0.4 is no longer supported.

As for your settings, preferences - queueing, preferences - bandwidth and preferences - bittorrent.

Link to comment
Share on other sites

@ DreadWingKnight - Loss of the 2.0.x interface is a bad thing. I found 2.2 to be very wasteful of desktop space, what with giant icons/buttons and an overly wide Label section. The font size and line spacing is the worst. Will those things be adjustable in the future?

I will still deny that Settings have anything at all to do with this, (download/upload speeds per torrent are my biggest concern) but here goes:

Queueing - Max Active (Up or Down) = 30, Max active Down = 50

Bandwidth - Global Max = 80, Alt. Max not in use. Max Down = 100, no check on limit boxes.

It is not this Global Max that is the problem. Although, this limit is being ignored occasionally.

BitTorrent - Only "Limit local peer" is unchecked.

BTW, I removed some 200 odd torrents to see if there was an overload problem. No change there.

Link to comment
Share on other sites

@ Switeck - The Force Starts seemed to get them moving faster. I didn't change them to Start later. I try to keep them running as long as possible to support the community. I try to be a good boy.

The Queueing is left over from when I was running 1.8.x. I agree that they don't go well together, but I don't run more than 25 active at a time anyway since I don't have I2 at the house (Oh, to dream...). I'll change that.

@DreadWingKnight - I had to load 2.2 on another PC to get details for you. Pictures are just a waste of time, not to mention the hassle of changing on this PC. Let's try using text.

Label Bar size problem

2.0.x has a straight list. That is perfect.

2.2 has a stupid File Tree setup with the equally stupid Icons that waste 8 character spaces, thus losing Main Window space when having to widen the Label section to see the labels! (You imply that I'm an idiot and can't adjust the label bar size. Not cool.)

The whole File Tree thing is just not needed. What was wrong with the sections of 2.0.x? It wasted little space and was perfectly functional. Why is the Label section tied to the Torrents section anyway? It could be better if Labels at least detached from the tree, but still not as good as the setup of 2.0.x.

Line Height problem

In the Files Tab, the leading (space between the lines) is HUGE! The Pieces graphic is also taller than the font now. These changes cause the loss of about 50% of the files that can be viewed in the same desktop space with 2.0.x. This is an extreme headache when managing torrents having more than a few files in them

Even the height of the tabs in the Main Window are taller. Wasting more space.

The color choices for 2.2 are horrible. The Red of the 2.0.x has become a glaring Orange/Red. The comfortable Green of 2.0.x has become Puke Green (otherwise known as Chartreuse)

=======================================

I'll try to get screen shots of the 2.0.x Settings later. It appears that the real problem is not going to be solved anyway. The detail of the problem having occurred before and going away on a reboot doesn't seem to have been noticed. It just won't go away now.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...