Help
Our table was closed because of the slowness of "Gib" - is this intentional?
Page 1 of 1
Money Bridge query Robot slowness
#2
- Group: Advanced Members
- Posts: 5,808
- Joined: 2003-January-15
- Gender:Male
- Location:USA
Posted 2006-April-12, 22:48
When a money bridge table is created, the table includes an option for "table speed". This setting determines how long the software will wait for a player to make a bid or play before giving up and closing the table.
We tried to make sure that even the Fast settings allowed enough time for GIB (the robot) to make calls. I have heard occasional reports that GIB sometimes does not respond in time.
This has two possible causes
- Something went wrong with the hand (bug) and gib was unable to play. Example: you lead the DA, holding the trick. Then you lead the DA to the next trick (assuming that a bug lets you do this, or makes us think this happened). Gib throws up its hands.
- GIB took a very long time to make a call. This could be because it was a complicated hand, or the machine hosting that GIB was temporarily overloaded. We have (relative to our needs) a conservative number of machines but it is possible that at that moment that machine was forced to run a large number of GIBs, slowing them all down to the point that one of them "timed out"
I will investigate further. What is your username on bbo (you can email me -- uday att bridgebase dott com if you don't want to say it here). Was it a "fun money" table or a real-money table ? Do you happen to remember who your opponent was, or the contract , or approx. when this happened? All this will help me track down the hand in our logs.
We tried to make sure that even the Fast settings allowed enough time for GIB (the robot) to make calls. I have heard occasional reports that GIB sometimes does not respond in time.
This has two possible causes
- Something went wrong with the hand (bug) and gib was unable to play. Example: you lead the DA, holding the trick. Then you lead the DA to the next trick (assuming that a bug lets you do this, or makes us think this happened). Gib throws up its hands.
- GIB took a very long time to make a call. This could be because it was a complicated hand, or the machine hosting that GIB was temporarily overloaded. We have (relative to our needs) a conservative number of machines but it is possible that at that moment that machine was forced to run a large number of GIBs, slowing them all down to the point that one of them "timed out"
I will investigate further. What is your username on bbo (you can email me -- uday att bridgebase dott com if you don't want to say it here). Was it a "fun money" table or a real-money table ? Do you happen to remember who your opponent was, or the contract , or approx. when this happened? All this will help me track down the hand in our logs.
#3
- Group: Members
- Posts: 17
- Joined: 2004-May-30
Posted 2006-April-12, 23:00
Username was "anzac" and it was a fun game. Unfortunately I don't remember my opponent or any other details - but it happened (IIRC) on 11th April around 5.30 - 6 pm (my time zone is GMT + 12).
Page 1 of 1