conquerist

azirevpn.net|SE rapid-telecom.net|BH

vqbn.com|SG

defoechan.com|HK

airwavebroadband.net|US jamalsoft.net|RU

fiberdirekt.net|SE ip-192-95-25.net|CA yundc.com|US

It looks like I'm not able to edit my post. sumofiber.com|US

jxgeoke.com|US (?) mingchenfood.com nbhopewell.com xiuqingjx.com xjjgaz.com yzhxsh.com yzsxkj.com zhaoshengzixun.com zsh88.com zslianshuo.com All those domains are rDNS entries for the range 108.62.225.0 - 108.62.225.255. The range 108.62.224.0/21 has been assinged by ARIN to Nobis Technology Group, LLC in Phoenix, Arizona. There are two "secondary assignments", 108.62.225.0/25 and 108.62.225.128/25, to Privax LTD in London, which is the company behind www.hidemyass.com. So, it's a proxy range that may be anywhere in the world. I looked for a placeholder or world flag in flags.bmp, but couldn't find one. "AQ" for Antarctica was as close to a placeholder as I could find. "US" would also make sense, because the servers appear to be located in Phoenix. tl;dr: It's a proxy server used by users around the world, run by a UK company, and hosted in the US.

ip-198-27-82.net|CA Some of the other ip-###-###-###.net, such as ip192-99-1.net are listed as FR. However, domaintools shows them as registered in Canada, and geoiptool.com also shows as as located in Canada. Does anyone have more information on whether these OVH domains should be FR or CA? OVH has recently built a large datacenter in Montreal, so CA seems plausible...

virginm.net|UK ip-192-95-26.net|CA The latter one really is apparently OVH Canada... http://whois.domaintools.com/ip-192-95-26.net

unitymedia.net|de

Windows XP SP3. I don't know whether the affinity setting has any relation to the "flushing to disk" issue. With "I see it for all cores", do you mean that you see the flushing to disk issue for all cores?Details on the core 0 affinity: There seems to be a bug in Windows XP, that sometimes on a clean boot, explorer.exe will start with affinity set to "core 0", and all child processes will also start on "core 0". So far the only problem that "core 0" affinity has caused was in VMware, which refuses to start any VM unless it has affinity set to both cores.

I've now had the same problem again, this time with 3.3 build 29544. I've noticed that the affinity of utorrent.exe was set only to one core, on a dual core system. I'm pretty sure that this was also the case the first time it happened (for details see quoted post).[edit] Please disregard this post. The problem also occurs with affinity set to both cores.

Added to original post (see edit #2).

Hi, I just upgraded from 3.2.1 to 3.3 build 29126 (newest build currently permitted on a certain tracker). I had uTorrent running for 23 hours and downloaded a 3.6 GB file. I checked on it just now and discovered the following: 1) The file is reported as having finished downloading. 2) Roughly the last GB has not been written to the disk yet, but is still in the cache. 3) The status of the torrent is "flushing to disk (68092)" 4) uTorrent is using ~1GB of memory. 5) uTorrent has used ~2 hrs of CPU time in 23 hrs of uptime. That's ~10% average CPU usage on a 1.86GHz Core 2 Duo. I've never had such high CPU usage with 3.2.1 or any older version. Now my questions a) is it intentional, that 1GB are written to memory cache and not to disk? is it intentional, that this cache is not written to disk when the download has finished? c) how do I get it to write this 1GB to disk without having to redownload it? d) is that high CPU usage normal with a 3.3 build? Thanks for reading this far. I'm sorry if what I'm reporting is already known, or if the potential bug(s) has already been fixed in a newer build. PS: Screenshots [edit] I just noticed the Disk Overloaded: 100% message. My disk usage during the download has been burning 2 DVDs and watching one movie. However, that was ~12 hours ago and the disk has been (to my knowledge) idle since then. [edit2] While downloading, uTorrent was unresponsive for ~10 seconds every 2 minutes. The pagefile was not in use, I think (physical memory in task manager always had ~1GB to spare). The cache size is set to 32MB. See screenshot #3. [edit3] In case it is relevant: all diskio.* settings under Preferences - Advanced are at their defaults. See screenshots #4 and #5. [edit4] 1) Disk write speed isn't an issue: download speed is ~250 kB/s, disk speed is ~50 MB/s, and there's plenty of free disk space. 2) 10 seconds every 2 minutes (see edit 2) with full CPU usage is where the 10% average CPU utilization comes from.

nlTelcom.com|NL

hotsplots.net|DE oikt.net|NO

lrcom.net|FR

dnsptr.net|US

portnetworks.net|US

cybersurf.net|CA mediateknik.net|SE *********************** w-link.net|US

internetadresi.com|TR ********************* cloud-ips.com|US dsn1.net|US keyoncom.com|US shoreham.net|US

5gdsl.com|UK

avenuebroadband.com|US

nbiserv.com|DE ****************** crestviewcable.com|US

skydebanen.net|DK ************************ vnet-inc.com|US gogrid.com|US xipline.com|US direcpath.com|US