Difference between revisions of "FAQ"
Jump to navigation
Jump to search
(Created page with "== Why do some Rust bots time out when playing in the IDE but not in the arena? == CodinGame decided to compile Rust programs in debug mode for matches played in the IDE and...") |
m (3 revisions imported) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | == What's the maximum submit rate? == | ||
| + | |||
| + | : There appear to be a soft limit (HTTP 522; CAPTCHA) and a hard one (HTTP 405). Are they puzzle-dependent? There's information about that sprinkled over the forum, but it's real hard to find again without more specifics :( [[User:JBM|JBM]] ([[User talk:JBM|talk]]) 12:39, 28 July 2020 (UTC) | ||
| + | |||
== Why do some Rust bots time out when playing in the IDE but not in the arena? == | == Why do some Rust bots time out when playing in the IDE but not in the arena? == | ||
CodinGame decided to compile Rust programs in debug mode for matches played in the IDE and in release (optimized) mode for arena matches. In Rust, there is an especially large difference between those two modes, because it is common to use high level features like iterators and higher-order functions that are slow in debug mode, but are optimized to very efficient machine code in release mode. In addition, arithmetic operations are checked for overflow in debug mode. Because of those, it is not rare for debug mode to be 10 times slower or more. This means that bots which are fine in the arena can often run out of time in the IDE. | CodinGame decided to compile Rust programs in debug mode for matches played in the IDE and in release (optimized) mode for arena matches. In Rust, there is an especially large difference between those two modes, because it is common to use high level features like iterators and higher-order functions that are slow in debug mode, but are optimized to very efficient machine code in release mode. In addition, arithmetic operations are checked for overflow in debug mode. Because of those, it is not rare for debug mode to be 10 times slower or more. This means that bots which are fine in the arena can often run out of time in the IDE. | ||
| + | |||
| + | == Can I lose points by winning a match? == | ||
| + | |||
| + | Yes, if you are very high (e.g. 40.0) and your opponent is very low (e.g. 5.0). See [https://wiki.faforever.com/index.php?title=How_Trueskill_works#Why_did_I_lose_points.2Fdon.27t_gain_point_with_a_win_.3F this explanation]. | ||
Latest revision as of 10:07, 15 June 2021
What's the maximum submit rate?
- There appear to be a soft limit (HTTP 522; CAPTCHA) and a hard one (HTTP 405). Are they puzzle-dependent? There's information about that sprinkled over the forum, but it's real hard to find again without more specifics :( JBM (talk) 12:39, 28 July 2020 (UTC)
Why do some Rust bots time out when playing in the IDE but not in the arena?
CodinGame decided to compile Rust programs in debug mode for matches played in the IDE and in release (optimized) mode for arena matches. In Rust, there is an especially large difference between those two modes, because it is common to use high level features like iterators and higher-order functions that are slow in debug mode, but are optimized to very efficient machine code in release mode. In addition, arithmetic operations are checked for overflow in debug mode. Because of those, it is not rare for debug mode to be 10 times slower or more. This means that bots which are fine in the arena can often run out of time in the IDE.
Can I lose points by winning a match?
Yes, if you are very high (e.g. 40.0) and your opponent is very low (e.g. 5.0). See this explanation.
