![]() |
why do i have to wait like 6000 sec? how do i set the wait til retry time. i'm on limewire 2.3.3 for Win XP... the time was less i believe but now it's 5000 - 6000 secs after the requery is sent. please help. thanx |
Could you imagine the traffic it would generate if an estimated 30,000 LimeWire nodes sent out queries every half an hour for each file they are downloading? Let's assume each node is trying to download 10 files, that would make 300,000 queries every half of an hour or 10,000 queries per minute. Can your connection handle 166 queries per second, when each search query + search results is - let's say 100 bytes? (That would make it ~16k/s in BOTH directions just for receiving and forwarding other people's searches). Ultrapeers would have to drop connections to cope with the traffic, which increases the distance between the nodes and your search queries can't reach hosts that are far away. That's why the time between requeries is set to a couple of hours. The amount of search results you receive are (simplyfied) inversely proportional to the amount of search traffic each client generate. If it was possible, the LimeWire developers would certainly reduce the time between requeries, but at the moment that would be extremely counterproductive. |
well the fast way is to kill the download and download again then it trys to connect right away... anyway I belive the time waiting for a requery gets higher by each interrotation. the first time its like 200 sec after those its like 600 and it gets higher.... each time. personally i don't like the requery send thing at all. ;) I don't really even know what it's for. I just guess it's some like push.... i don't think you can set it manually anywhere. |
Quote:
|
All times are GMT -7. The time now is 12:30 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.
Copyright © 2020 Gnutella Forums.
All Rights Reserved.