[CQ-Contest] Forum topic

[Ed W0YK]

Current log checking software takes literally 2-3 minutes to fully process a few thousand logs with a few million QSOs, including all the results tables.  A moderate performance office PC is sufficient. Cleaning up log errors takes hundreds of volunteer hours before the final minutes-long computer run.  And, of course, gathering photos and information to create the results article is time-consuming.Log checking software is custom-created and supported by a few very smart volunteers.  Running time is inconsequential in the overall contest results process.73,Ed W0YK
-------- Original message --------From: Steve Dyer via CQ-Contest <cq-contest at contesting.com> Date: 8/16/21  05:19  (GMT-08:00) To: cq-contest at contesting.com Subject: Re: [CQ-Contest] Forum topic These days that's a pretty small data set. It fits in memory easily and if I recall, each complete run only takes a minute or two. I saw a presentation about it somewhere from K5ZD.This is not trivializing the programming, it's just not a scale problem anymore.73,SteveW1SRDOn 8/15/2021 14:54, Richard F DiDonna NN3W 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 at contesting.com> http://lists.contesting.com/mailman/listinfo/cq-contest_______________________________________________CQ-Contest mailing listCQ-Contest at contesting.comhttp://lists.contesting.com/mailman/listinfo/cq-contest