Phex settings hurting the network

[et voilà]

Salut GregorK, it has been pointed to me in the French forum that Phex allows up to 99 connections when being a leave. This is unacceptable. Phex should enforce the option to be between 1-5 connections to UP when a leave. Also, Phex should enforce common settings while being an UP: Between 20-40 intrapeer connections and 20-40 leaves (because of the 64KB QRT Phex is using). I hope those settings are enforced in the next Phex release because as of now, there is TOO much room for abuse.

Ciao

[GregorK]

Oups... I assumed there was a limited of 9, but it looks like it got lost somewhere in the code.
I adjusted it to max 5.

I have not spend much time thinking about it, but I dont really see the relation between QRT and number of connections. Only for a possible upper limit for QRT aggregation maybe.

I agree that Phex handles a few settings more lax then some other clients do, and I agree that there should be some restrictions about it to not allow too much abuse.
But Phex was and will always be aimed to a small and more advanced user audience, therefore there will always be less restrictive configuration options.
On the other hand this might cause that unexperienced user will not get good results with Phex since certain features will not work when configuration values are not in range, like Limes "GoodHost" rating...

I hope you can accept that we like to give the user more freedom, but of course we also like to limit an overly abuse.

Gregor

[arne_bab]

Hi ét voila,

Could you give some more info on optimal settings?

How long should Phex wait (as defautl), before it recognizes a host as down? (At the moment at 8s, iirc).

How many simultaneous connections to uploaders are preferable (and how many for each single file)?

What Push timeout?

[et voilà]

Salut GregorK: yes I realize Phex is targetting a more advanced userbase and that the impact of Phex users is currently small, but this is no reason to not enforce good behavior in the network (99 connections leave connections to UPs = the impact of 33 LW leaves and 50 Bearshare leaves...). Anyway good to hear it is fixed in the CVS, you are more responsive than other P2P devs


Just FYI, as UP
Bearshare: 26 intra UP connections and 65 leaves
LW: 32 intra UP and 30 leaves
As leave:
Bearshare: 2 UP connections
LW: 3 UP connections

Going outside those limits is risky as to the efficienty of the current network topology.
The 64KB QRT is only limiting for the number of leaves an UP should allow, more than 40 would create a lot of false positive by filling too much the QRT.

-------

Salut arne_bab, I'll try to answer those questions the best I can

1) you mean as a host leave without Bye packet? I believe 60-120 seconds without answers would discredit a left or unresponsive host. However not sure of what you mean

2) For downloads, 6-10 simultaneous hosts should be used by Phex for EACH download, this includes current downloads sources + the number of hosts you are queued into (number of hosts you are dling one file from + hosts you are into their queue for that file< 6-10 hosts)
For uploads, concurrent uploads to same users should be between 1 and 3. I personnaly think the upload slots by default should allow each downloader to get at least 2 KB/s, ie 20KB/s upload capacity = max 10 upload slots.
The queue should be no longer than 10, more = waste of downloaders time + waste of bandwidth.

3) Push? Do you mean push proxies or old Gnutella pushes (not sure of what Phex supports...) I'm not sure about that one, old pushes should maybe be 120 seconds while push proxies should nrmally be much faster, say 60 seconds (I think someone should look into LW source code or GTK-Gnutella source).

Ciao

[arne_bab]

Hi et voilà,

thanks for the answers.

to 1) I mean, when establishing a connection (handshaking). How long should phex wait before marking a hosts as offline?

Phex uses PushProxy, so 60s should be fine.

Thanks for the infos!

@Gregor: Could you increase the number of maximum connections to 24 then? That should make downloading more efficient for most users and means about 8 hosts per download, iirc. (I'd do it myself, if I had an internet-connection at home at the moment).

[et voilà]

Salut arne_bab, normally handshaking should be done within 10 seconds. If you want responsive hosts you could go as low as 5 seconds.

Ciao

[arne_bab]

Thanks!