![]() It also matters a LOT for the time sync operation which makes sure JBidwatcher has a good idea of what eBay's official time is, compared to your computer's clock. This matters for login, and placing the actual snipe. " The other problem is latency with all the traffic being generated, the operating system needs to inject the JBidwatcher request packets into the stream, such that they don't collide with any other packets being sent/received, and then has to process the return responses from eBay. It's been almost a year since I last torrented anything, and I still get pings on those ports. I often wish I could block traffic at the OTHER end of my DSL connection, so those stopped using my bandwidth. " Worse, in my experience, once you've run a torrent client/Vuze/Azureus, especially as a seed, your IP address is in torrent files all over the place and even if you're not running a torrent anymore you'll be getting random attempts to connect to your torrent ports. If you haven't set a max, it'll flood your network card/DSL, and 'll be hard to get traffic through that.) 5MB/s (bytes), and (as I recall) Vuze measures in K/s (K-bytes, not bits), so if you have your bandwidth usage max set to download at 100K/s then you have an effective 400K/s link. (So if you have 5Mbps (bits), that's an effective. You'll get a bit more overhead, from other clients trying to connect and being turned away, but you can effectively treat your pipe as having that much less bandwidth. If you have limited your up/down usage, then the torrent app will try to saturate that much usage. On a home connection, unless you've drastically limited your up/down bandwidth, it'll definitely slow down JBidwatcher's ability to communicate to eBay. I know this because I did it once at work, accidentally. The number of packets, and the size of those packets, sent and received by a torrent program are sufficient to saturate a small internet company's Internet pipe. " Torrent activity will definitely cause problems for sniping. To quote Morgan Schweers' analysis () on why it's not even enough to temporarily completely cease torrent activity to facilitate a snipe: Has anybody here managed to reliably snipe whilst seeding torrents ? I was most grieved to have to give up running Vuze on my PC because all the extra traffic it generated caused JBidwatcher (no web GUI either FTR) to snipe far too late where it would have otherwise won me the item - not tightly-timed ones, I might add, but default-set for -30s. Slightly off topic but a reality check against likely demand is the practicality of sniping for those who (like me) want to continue doing their bit for the torrent community.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |