Just one snipe fired yesterday
Brought to you by:
cyberfox
Menu
▾
▴
#724 Just one snipe fired yesterday
Hi Cyberfox,
yesterday I tried to make JBidWatcher snipe on various
auctions from one seller. Lokk at the log:
---snip---
Wed Aug 10 19:53:29 CEST 2005: Wed Aug 10 19:53:29 CEST
2005: 7339661680 (SW87 Vollmer N 2-teiliges Geb�deset,
ansehen!) - Executing snipe! (1)
Wed Aug 10 19:53:29 CEST 2005: Bidding 4.47 on 1
item[s] of (7339661680)-SW87 Vollmer N 2-teiliges
Geb�deset, ansehen!
Wed Aug 10 19:53:29 CEST 2005: Wed Aug 10 19:53:29 CEST
2005: 7339661680 (SW87 Vollmer N 2-teiliges Geb�deset,
ansehen!) - Loading item... (1)
Wed Aug 10 19:53:40 CEST 2005: Wed Aug 10 19:53:40 CEST
2005: 7339661680 (SW87 Vollmer N 2-teiliges Geb�deset,
ansehen!) - Done loading item... (1)
Wed Aug 10 19:53:40 CEST 2005: Wed Aug 10 19:53:40 CEST
2005: 7339661680 (SW87 Vollmer N 2-teiliges Geb�deset,
ansehen!) - Loading bid request... (1)
Wed Aug 10 19:53:41 CEST 2005: Checking sign in as bid
key load failed!
Wed Aug 10 19:53:41 CEST 2005: Wed Aug 10 19:53:41 CEST
2005: 7339661680 (SW87 Vollmer N 2-teiliges Geb�deset,
ansehen!) - Snipe attempt completed. (1)
Wed Aug 10 19:53:41 CEST 2005: Wed Aug 10 19:53:41 CEST
2005: 7339661680 (SW87 Vollmer N 2-teiliges Geb�deset,
ansehen!) - Snipe was too low, and was not accepted. (1)
Wed Aug 10 19:53:41 CEST 2005: Snipe was too low, and
was not accepted.
Wed Aug 10 19:53:41 CEST 2005: Wed Aug 10 19:53:41 CEST
2005: 7339661718 (SW88 Vollmer N 4-teiliges Geb�deset,
ansehen!) - Executing snipe! (1)
Wed Aug 10 19:53:41 CEST 2005: Bidding 3.19 on 1
item[s] of (7339661718)-SW88 Vollmer N 4-teiliges
Geb�deset, ansehen!
Wed Aug 10 19:53:41 CEST 2005: Wed Aug 10 19:53:41 CEST
2005: 7339661718 (SW88 Vollmer N 4-teiliges Geb�deset,
ansehen!) - Loading item... (1)
Wed Aug 10 19:53:48 CEST 2005: Wed Aug 10 19:53:48 CEST
2005: 7339661718 (SW88 Vollmer N 4-teiliges Geb�deset,
ansehen!) - Done loading item... (1)
Wed Aug 10 19:53:48 CEST 2005: Wed Aug 10 19:53:48 CEST
2005: 7339661718 (SW88 Vollmer N 4-teiliges Geb�deset,
ansehen!) - Loading bid request... (1)
Wed Aug 10 19:53:49 CEST 2005: Wed Aug 10 19:53:49 CEST
2005: 7339661718 (SW88 Vollmer N 4-teiliges Geb�deset,
ansehen!) - Done loading bid request, got form... (1)
Wed Aug 10 19:53:49 CEST 2005: Wed Aug 10 19:53:49 CEST
2005: 7339661718 (SW88 Vollmer N 4-teiliges Geb�deset,
ansehen!) - Submitting bid form. (1)
Wed Aug 10 19:53:51 CEST 2005: Wed Aug 10 19:53:51 CEST
2005: 7339661718 (SW88 Vollmer N 4-teiliges Geb�deset,
ansehen!) - Done submitting bid form. (1)
Wed Aug 10 19:53:51 CEST 2005: Wed Aug 10 19:53:51 CEST
2005: 7339661718 (SW88 Vollmer N 4-teiliges Geb�deset,
ansehen!) - Loading post-bid data. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339661718 (SW88 Vollmer N 4-teiliges Geb�deset,
ansehen!) - Done loading post-bid data. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339661718 (SW88 Vollmer N 4-teiliges Geb�deset,
ansehen!) - Snipe attempt completed. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339661718 (SW88 Vollmer N 4-teiliges Geb�deset,
ansehen!) - You have been outbid in your snipe on SW88
Vollmer N 4-teiliges Geb�deset, ansehen! (1)
Wed Aug 10 19:53:57 CEST 2005: You have been outbid in
your snipe on SW88 Vollmer N 4-teiliges Geb�deset, ansehen!
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339661725 (SW90 Vollmer N 2-teiliges Geb�deset,
ansehen!) - Cancelling snipe, time is suddenly past
auction-end. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339661725 (SW90 Vollmer N 2-teiliges Geb�deset,
ansehen!) - Cancelling snipe. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339661990 (SW73 Faller/Vollmer N
Bekohlungsanlage & Bahnsteig) - Cancelling snipe, time
is suddenly past auction-end. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339661990 (SW73 Faller/Vollmer N
Bekohlungsanlage & Bahnsteig) - Cancelling snipe. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339661997 (SW71 Faller/vollmer N Stellwerk &
Dampflokschuppen) - Cancelling snipe, time is suddenly
past auction-end. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339661997 (SW71 Faller/vollmer N Stellwerk &
Dampflokschuppen) - Cancelling snipe. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339662009 (SW78 Vollmer N 6-teiliges Geb�deset
(Bahnanlagen)) - Cancelling snipe, time is suddenly
past auction-end. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339662009 (SW78 Vollmer N 6-teiliges Geb�deset
(Bahnanlagen)) - Cancelling snipe. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339662020 (SW79 Faller/Vollmer N 4-teilges
Industriegeb�deset) - Cancelling snipe, time is
suddenly past auction-end. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339662020 (SW79 Faller/Vollmer N 4-teilges
Industriegeb�deset) - Cancelling snipe. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339662077 (SW84 Busch N 7097 Star�nbau-Set) -
Cancelling snipe, time is suddenly past auction-end. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339662077 (SW84 Busch N 7097 Star�nbau-Set) -
Cancelling snipe. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339662112 (SW91 Faller N 3-teiliges Bahnsteig
Konvult, ansehen!) - Cancelling snipe, time is suddenly
past auction-end. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339662112 (SW91 Faller N 3-teiliges Bahnsteig
Konvult, ansehen!) - Cancelling snipe. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339662219 (SW74 Kibri/Vollmer N E-Lok-Schuppen /
Gterschuppen) - Cancelling snipe, time is suddenly past
auction-end. (1)
Wed Aug 10 19:53:57 CEST 2005: Wed Aug 10 19:53:57 CEST
2005: 7339662219 (SW74 Kibri/Vollmer N E-Lok-Schuppen /
Gterschuppen) - Cancelling snipe. (1)
---pins---
As you may see, I bid on "ebay.de" ;-)
On the "complete" tab, I do not see the amount of any
snipe, just the amounts of the high bids. In older
versions, I still saw the amount of my bid in () when
the snipe was not successful.
I am not amused, since I sniped higher amounts as most
of those items were sold for...
Regards
Werner
Logged In: YES
user_id=19745
Greetings,
Wow. You tried a simultaneous snipe for *10* items? With
what looks like a snipe timing of about 20 seconds out. If
it were to work, that'd be an average of 2 seconds per
snipe. However it took 11 seconds to load the first item,
and 7 seconds to load the second. It didn't even try to
load any of the later ones, because the time was already
past-due.
It actually successfully sniped on two of the items, not
one, but your bid was too low for either of them (one it was
too low before the bid, the second someone else's proxy bid
was higher).
The other items, 7339661725, 7339661990, 7339661997,
7339662009, 7339662020, 7339662077, 7339662112, and
7339662219 JBidwatcher never had a chance.
This is a bit hard to explain, but JBidwatcher has a single
thread for doing snipes, and a single thread doing updates.
If it had multiple threads, they'd potentially conflict
with each other, at the very least on the networking layer,
so having it serialized makes the most sense. (I'm not
actually positive that Java doesn't serialize network access
on a synchronized object someplace down deep anyway (it
certainly has felt like it sometimes during JBidwatcher
development, but it seems like it would be such a wrong
design decision) in which case multiple threads would be
useless.)
Plus it's VERY rare for someone to want to bid on more than
1 or 2 items that are ending at exactly the same time. Also
with enough leeway, as in this case, JBidwatcher can handle
it. Bidding on 10 items, you'd have to give JBidwatcher a
lot more leeway to do its sniping for each item. Adding the
affiliate load into it, as described on my blog, it starts
taking a lot too long.
I don't actually know what JBidwatcher could have done
differently here. I'll think about a rearchitecture of the
bidding code for JBidwatcher 2.0, and perhaps I can come up
with something faster, more streamlined, and better able to
handle multiple simultaneous snipes.
-- Morgan Schweers, CyberFOX!
Logged In: YES
user_id=19745
Originator: NO
Greetings,
Bugs filed before 1.0 and bugs without responders are being juggled in terms of priority (9 is highest priority). I'm raising bugs filed with a submitter, post-1.0 to P6. Bugs which are filed post-1.0, but without a submitter are P5. Before 1.0 bugs with a submitter are becoming P4, and pre-1.0 bugs without a submitter name become P3.
If the bug is still relevant, and has a watcher (i.e. you got notified when I changed this bug), feel free to bubble it back up again.
Email addresses in bugs are great, but I can't always respond via email. Sometimes, especially for duplicate bugs, I use automated tools (like I'm doing right now) to change status on a large number of items at once.
Thanks for your patience, while I try to pare back the bug list to what may actually still be in the program.
-- Morgan Schweers, CyberFOX!