Gixen bid log

[vonkuttenberg]

hello Mario, first thanks for this great service, i am not used to pay for internet stuff, but your program (mainly thanks your community support - it fascinated me so much) that i quit from not very well workin BayGenie and signed to your "premium" server.

My question is if there is any way or feature for seeing log of bid as you are answering here to every second person complaying "WHY HE DID NOT WON"?

something like:
AUCTION ENDS 9.2.2011 09:32:14
09:32:10 LOGGIN
09:32:11 SUCESSFUL
09:32:12 LOOKING FOR HIGHEST BID
09:32:12 HIGHEST BID IS 57.4$
09:32:13 BIDDING 59$
09:32:13 OKAY YOU ARE HIGHEST BIDDER 59$
09:32:14 LOOKING FOR HIGHEST BID
09:32:15 AUCTION ENDED

that would be really great to understand me the principle of your service. I switched my servers to 3sec before finish because i think all algoritm are prepared to bid later than 6second before end and i am quite suprised that according to red text "you really dont suggest 3sec bidding"

[Cupid]

Gixen logs in much earlier than you suggest, it also checks for the highest bid after the auction ends, because there may be later bids than the one it submits (if it is able to).

3 second snipes have a greater risk of being late due to factors outside Gixens control, like network latency.

Since sniping only protects you from bidders that react to your bid it is only necessary to be late enough to prevent that happening, 6 seconds is ample time for this. Certainly there can be later bids but these were (in the vast majority of cases) going to be placed anyway and are not reactions to your bid. In these cases it is actually an advantage to have bid earlier as you gain the advantage of the bid increment and first bid rules.
_________________
Mark

[vonkuttenberg]

okey i am starting understanding system of how does it work. is there any post where is explained how the systems works with lastmoment bidding? (because i am really confused of ebay log of last moment bidders like

for example auction ends at 12:15:05 aaand:

12:13:03 b***b 68$
12:15:25 y**t 72$
12:15:03 z***t 56$
12:15:01 x***y 55$


and your 6seconds before end means that 6secs it get info about highest bid and bid in last 5seconds or it means that 6seconds before end it bids? or it reads highest bid 6secs before and wait for last moment?

[Cupid]

Some of the details about exactly how Gixen works are commercially sensitive and hence are not made public.

The log that you posted is not possible because it states that the last bid at 12:15:25 happened after the auction ended at 12:15:05, unless the bid at 12:15:25 was on a previous day?

If you have a bid scheduled with a 6 second offset Gixen obtains the current auction price before that and attempts to place the bid 6 seconds before the auction ends when the current auction price, that it detects, is lower than the bid to be submitted.
_________________
Mark

[vonkuttenberg]

okay i missunderstood a bit. can you explain me this on a direct link

offer.ebay.de/ws/eBayISAPI.dll?ViewBids&item=180612896924

the winner overbid the highest bid before he add it

[Cupid]

OK from your link, the auction ended at 25.01.11 15:04:11 MEZ, the winning bid was placed at 25.01.11 15:04:05 MEZ and the second highest bid was placed at 25.01.11 15:04:07 MEZ.

So what happened was that the winning bid was placed 6 seconds before the end, the second highest bid was placed 2 seconds later (4 seconds from the end of the auction) but was outbid by the earlier bid, the price was increased to that bid plus one bid increment.

The losing bid could not have been a reaction to the one that won though because 2 seconds is not enough time to make a decision and then make a bid.

I can't see anything unusual, can you? That is how eBay display bids, the lowest at the bottom the highest at the top... it does not display them in the order that they were placed timewise.
_________________
Mark

[mario]

vonkuttenberg,

In fact most of it is not a secret:

1) Gixen logs in some time before auction end. This varies from 30 to 90 seconds. I experimented with different values, but not because it makes any difference for users - mostly to tweak performance of my servers. Bid offset is the actual time when final confirmation of the bid is sent. Logging in, going through the flow, etc, obviously has to be done before that.

2) I have these logs, but I am not going to make them directly available, as logs alone would not be much useful to most users, and searching through them (by users) would certainly affect servers with little or no benefit. When in doubt, I prefer users to contact me, and then I will investigate.

[Cupid]

Yes, I didn't mean to imply that the methods are secret only that Mario does have some intellectual property tied up in the implementation of those methods (hence the copyright on the Gixen pages).
_________________
Mark

[mario]

Mark, when you say it that way, you give it too much importance... sure, I wouldn't publish the code, yet somehow I still don't see any sniping software as something overly inventive. Its challenge really is making it scale for a large number of users (something I always enjoyed - making lean and efficient software), and polishing it to the point that reliability is at its maximum.

Below is the "uptime" of the mirror server. 1211 days without reboot.

[root@gate ~]# uptime
20:13:33 up 1211 days, 20:25, 4 users, load average: 0.11, 0.17, 0.20
[root@gate ~]#

[Cupid]

That is an impressive statistic... Is it Unix or Linux?
_________________
Mark

[mario]

Linux, all Gixen servers are running under Linux.

[User]

Thank you Mario for doing this!!!!!!!!!!!!!

[jimsurf]

This site kicks azz!

[RECODO53]

GIXEN IS A FRAUD....I LOOSE MY 6 DLLS AND MORE ON ITEMS 320739330865 AND OTHERS.....

[mario]