FAQ - Big ask for explanation a few uTorrent settings

[descra]

hi all,

Ability of reading isn't strange to me but in my opinion FAQ doesn't explain strictly all the uTorrent settings.

so ... I've got an ask to you to help me understand a few options witch I think should be explain more precaisly.

1. net.wsaevents - "is an option to tweak if you are having weird firewall problems. Lower the value one by one to see if it makes any difference"

(FAQ)

What kind of problems this option "tweaks" ?

Why the default value is set to 6 and what that "6" means?

... and what it will be means when I set it for example on 4 or 1 ..... or 10 ?

For what this setting is exactly responsible?

2. bt.compact_allocation - "This allows µTorrent to create files in a Python-like manner to save space. You CANNOT use this option in conjunction with the partfile"

(FAQ)

Why exactly this option CAN NOT be use in conjunction with another option "partfile" ?

What could be the resaults if this both options will be Turn ON at the same time ?

Is it dangerous or something?

3.bt.send_have_to_seed - "This turns on/off sending have messages to seeders"

(FAQ)

What kind of messages is goin' about ?

for example: "Hi John, how are you? wish you a very nice day" or very important things like when my bittorrent client automaticly "ask" another client if he's got some interesting me part of some files witch he could send me?

4. diskio.coalesce_writes - "tries to minimize the number of calls to WriteFile. It doesn't have any effect at all on download speed, but it might cause marginally less disk writes (at the expense of more memory / CPU)

(FAQ)

I understand that it doesn't have any effect on download speed but when I read that "it might cause marginally less disk writes" so I'm wondering if it does have some effect on bigger number of "wasted data" ? ... cause maybe some pieces aren't write to disk and they are treated like "wasted data" cause uTorrent trying to decrease number of disk writes, some pieces ignor ?

Is this posible?

... because when the download speed is the same so something has to happend with some downloaded pieces

Are they put it in to the queue and they have to wait to be finaly write to disk or something else is happend to them? for example they are not write to disk and simply "vanish" in the name of "wasted data"

thanks in advance for your answers

[Ultima]

1. lol I don't think much is known about it... I'll try asking ludde, as I've been trying to for a while now.

2. It causes various problems, "Element not Found" being one of them, if I'm not mistaken. And then you can't download.

3. ... there's always messages sent between BitTorrent clients to communicate and facilitate coordinated transfer... that just disables sending the message identifying you as a seed to other seeders, presumably to save *some* bandwidth (not sure exactly why).

4. Wasted data is redundant data that is tossed out, so the answer is, no, it doesn't increase redundant data.

[wyrmchild]

@ultima

You are wrong for number 3, the have message is sent to all your connected peers when you finish single(!) piece, efficiently stating that you can seed that one (too). Nothing to do with you being identified as a Seed, only a leecher with one more piece to share.

Sending Have messages to seeds is not very useful, though (IMO), as it bears little meaning to them (AFAIT), unless they're tracking how well others are seeding (which is a waste of resources, as they can't possible tell who gave the data for that piece to get completed, except when they sent some of it).

Super-seeds are perhaps the only ones who benefit from this, but last time I checked how super-seeding works, they lie about the number of pieces they have to everyone, causing an odd hole in the availability of data (and effectively making them look like [and be identified as] leechers, that never download anything from anyone).

And as a last bit, the only messages that identify you as Seed are Bitfield (sent only right after handshake) with all the bits set (indicating you have all the pieces), sending enough Have messages (for all the pieces that you didn't have in the Bitfield), and the Have All message which was introduced with the Fast Extension (which isn't implemented in uTorrent, yet?).