Post History
If restricting everyone to the same system, then we can force every contestant to use https://tio.run and the on-site bench-marking found below "debug" -> "real time" as efficiency metric. Examp...
Answer
#2: Post edited
If restricting everyone to the same system, then can force every contestant to use https://tio.run and the on-site bench-marking found below "debug" -> "real time" as efficiency metric. [Example](https://tio.run/##S9ZNT07@r5yZl5xTmpKqYFNckpKZr5dh9z8zr0QhNzEzT0GjLD8zRZOrmktBoaC0pFhDKSM1JydfoTy/KCdFUUnTmqv2//9/yWk5ienF/3X9jQE).- Advantages:
- - No matter how (in)accurate, this gives everyone the same conditions and the same bench-marking system. It is fair.
- - Multiple programming languages and compilers are possible. Competitions between solutions in the same language and/or other languages is possible.
- - We already use TIO for most challenges.
- Disadvantages:
- - Heavily biased towards a specific target - I think it runs on x86_64 Linux?
- - Execution times are rather arbitrary with poor accuracy. This is a poor benchmarking tool by professional standards, but maybe for this purpose we don't really care?
- If restricting everyone to the same system, then we can force every contestant to use https://tio.run and the on-site bench-marking found below "debug" -> "real time" as efficiency metric. [Example](https://tio.run/##S9ZNT07@r5yZl5xTmpKqYFNckpKZr5dh9z8zr0QhNzEzT0GjLD8zRZOrmktBoaC0pFhDKSM1JydfoTy/KCdFUUnTmqv2//9/yWk5ienF/3X9jQE).
- Advantages:
- - No matter how (in)accurate, this gives everyone the same conditions and the same bench-marking system. It is fair.
- - Multiple programming languages and compilers are possible. Competitions between solutions in the same language and/or other languages is possible.
- - We already use TIO for most challenges.
- Disadvantages:
- - Heavily biased towards a specific target - I think it runs on x86_64 Linux?
- - Execution times are rather arbitrary with poor accuracy. This is a poor benchmarking tool by professional standards, but maybe for this purpose we don't really care?
#1: Initial revision
If restricting everyone to the same system, then can force every contestant to use https://tio.run and the on-site bench-marking found below "debug" -> "real time" as efficiency metric. [Example](https://tio.run/##S9ZNT07@r5yZl5xTmpKqYFNckpKZr5dh9z8zr0QhNzEzT0GjLD8zRZOrmktBoaC0pFhDKSM1JydfoTy/KCdFUUnTmqv2//9/yWk5ienF/3X9jQE). Advantages: - No matter how (in)accurate, this gives everyone the same conditions and the same bench-marking system. It is fair. - Multiple programming languages and compilers are possible. Competitions between solutions in the same language and/or other languages is possible. - We already use TIO for most challenges. Disadvantages: - Heavily biased towards a specific target - I think it runs on x86_64 Linux? - Execution times are rather arbitrary with poor accuracy. This is a poor benchmarking tool by professional standards, but maybe for this purpose we don't really care?