The biggest contest so far had over 4,500,000 qsos (CQWW CW 2019).
WWROF stepped up a few years back and provided a hefty machine with 32
cores and 256GB of memory to get the job done. It is located in a
commercial hosting center with the failsafes one would expect. This is the
same cqww.com that serves all the CQ Contest web pages (tnx to K5ZD). Dave,
KM3T and Geo K5TR are the IT geniuses behind it.
The code is heavily multithreaded C++, and optimized for speed over memory
use, so we are still under two minutes of run time for the biggest CQ
Contests. However, when we enable the modules used to detect cheaters, run
time can be up to an hour.
We don't discuss algorithms used to detect cheaters, don't ask! 😀
- Ken K1EA
CQWWCC member
On Sun, Aug 15, 2021 at 6:07 PM Richard F DiDonna NN3W <richnn3w@gmail.com>
wrote:
> Has anyone ever done a Dayton forum or online forum on contest log
> checking? In briefly chatting with KL9A regarding the number of logs that
> get submitted (over 1,000 in some NAQP events), it dawned on me that it
> requires a little computing power to have a database of 2,500,000 QSOs
> (assuming 1,000 logs with an average of 250 QSOs per log for NAQP) or a
> database of 25,000,000 QSOs (assuming 5,000 logs and an average of 500 QSOs
> per log for CQWW).
>
> How long does the log checking actually take and what database programs are
> used these days?
>
> 73 Rich NN3W
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
>
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|