uTorrent 3.1 very slow to present UI with large ipfilter.dat

[d18c7db]

I was using utorrent 2.2.1 up until today when I finally upgraded to 3.1 and I immediately noticed that when starting utorrent 3.1, the UI does not appear right away. The utorrent process sits there consuming about 50% CPU and 18M of RAM.

I immediately suspected my ipfilter.dat file and removed it and sure enough utorrent 3.1 starts and presents the UI immediately. With the ipfilter.dat back in it takes roughly about 10 minutes from running the .exe until the UI appears.

My ipfilter contains a large amount of entries:

[2012-01-16 20:35:58] Loaded ipfilter.dat (285713 entries)

I know there are divided opinions on the usage of ipfilters and I really don't want to start a discussion on the pros and cons of it, my question is a very simple one:

Based on the simple fact that 2.2.1 used to start up in under 3 seconds and 3.1 takes 10 minutes with the same exactly ipfilters file, is there a fix that the developers are willing to look at towards improving the performance of 3.1 to what it used to be in 2.2.1 in this respect, pretty please?

I love utorrent and it would be nice to keep using the latest version without being forced to revert to 2.2.1 if at all possible.

Regards and thanks to the developers for all the hard work.

[d18c7db]

Sorry I was mistaken, I didn't go from 2.2.1 to 3.1 but in fact from 1.8.5 to 3.1 so it appears that this has been broken since version 2.0

I'm a little sad that this isn't something developers are willing to look at given they already had it working fine in early versions. I've now downgraded back down to 1.8.5 so I'll be using that for as long as possible.

[schnurlos]

I'm using an ipfilter.dat too (since ever), have 313646 entries atm, but never noticed any delay on starting utorrent. I really run all versions and builds (alphas, betas, RC's and sometime stable versions ) and never had any problem with the ipfilter.dat, not on XP or Windows 7.

So this was never broken, perhaps your ipfilter.dat is.

[d18c7db]

You may well be correct, could we perhaps exchange ipfilter files and I could test with yours and you with mine? You can email me at hotmail if you wish, same username as here.

Also just last weekend I rebuilt my system, I used to run Win 7 x86 and went to a fresh install of Win 7 x64. Even on a fresh install, the behaviour remains the same, where 1.8.5 loads within a few seconds while anything > 2.0 just sits there for minutes.

Thank you for your response.

[schnurlos]

http://www.should.keepfree.de/ipfilter.rar this is what I use.

Just mail me yours: utorrent (at) gmx dot at

[schnurlos]

Backmail sent.

[Firon]

ipfilter loading was really broken in 2.2.1. That's why it was fast. It didn't actually WORK correctly.

We fixed the bugs, but it did result in a pretty big performance penalty.

[d18c7db]

Thanks Firon, that makes sense, also Schnurlos pretty much solved my problem. With the filter at the link he posted above, utorrent 3.1.2 now loads up in about 10 seconds. The ipfilter file contains 313646 entries.

The problem as explained by Schnurlos is that my ipfilter contained multiple overlapping IP ranges which Schnurlos was kind enough to outline below:

000.000.000.000 - 000.255.255.255 , 000 , futile because of line 2

000.000.000.000 - 002.255.255.255 , 000 ,

001.000.001.000 - 001.001.000.255 , 000 , futile because of line 2

001.001.002.000 - 001.002.002.255 , 000 , futile because of line 2

001.002.004.000 - 001.049.255.255 , 000 , futile because of line 2

001.050.004.000 - 001.254.255.255 , 000 , futile because of line 2

002.000.000.000 - 003.255.255.255 , 000 , half of this is covered in line 2

003.000.000.000 - 003.255.255.255 , 000 , futile because of line 7

etc...

If anyone else is having this same problem, you need to get an ipfilter that has unique IP ranges and your problem will be solved.

Thank you all for your help