I'm running v1.2 on an Athlon64 on Suse 10.1beta 64 bit

After upgrading the os and KT I've noticed that when KT is running, even though it's limited to less then 1/2 total available bandwidth and is only dl'ing at 5-10KB that my browser(s) is being limited in how fast it can dl. If I quit KT browsing returns to normal.

This was not an issue using the 32bit version on a 32 bit os.

I have tested both the available 64bit rpm and one I compiled and they behave the same.

thanks,

Interesting ... you are not the first one to report this. Maybe the other people who have run into this problem can confirm if they are running a 64 bit PC.

I myself run a 64bit amd, haven't noticed any slowness in browser performance. I will examine it some more in the weekend..

(64 bit AMD, Kubuntu 5.10, KT compiled from svn)
I didn't notice that behaviour, I just tried and when KT is unleashed browsing becomes nearly impossible but after KT is limited, I can browse super fast and emails downloading from the POP server is a snap...

When you have to limit KT, what do you have to limit, upload or download ? Or both ?

Also did you pass any special options to configure, when you compiled it ?

Since I have an asymetric DSL, I normally limit the upload rate to 80% of the available upward bandwidth, down speed is not a problem.

jyhelle wrote:Since I have an asymetric DSL, I normally limit the upload rate to 80% of the available upward bandwidth, down speed is not a problem.

You may set it to 80 %, but that is only on the upload speed of data, there is other stuff being uploaded (protocoll messages) which will take some more bandwith.

I haven't noticed any issues running version 1.2 on gentoo, amd64 [if that helps]
so maybe something distro specific?

Mith wrote:I haven't noticed any issues running version 1.2 on gentoo, amd64 [if that helps]
so maybe something distro specific?

Me neither, and I also have a amd64 running kubuntu.

George wrote:You may set it to 80 %, but that is only on the upload speed of data, there is other stuff being uploaded (protocoll messages) which will take some more bandwith.

Yes, that's why I use that 80%, which is totally empirical, but leaves some room for the protocol and my own traffic when browsing - that is I occasionally type a 30 characters URL, and since I get dozens of kBytes to read in response I'm too busy to send other data for a while