That being said, on
a busy band I think it is reasonable and normal to see it take a
couple of seconds into the next receive period before all of the
decoding and JTAlert processing is completed. There is a lot of
heavy number-crunching involved in decoding these signals.
73,
Rich VE3KI
Also, the OP mentioned JTDX which can be a real
CPU hog if it hasn't been configured correctly. JTDX has an
extended set of decoding options (compared to WSJT-X) in an effort
to pull out more weak decodes. These additional decoding options
involving number of threads and cpu cores used, if not configured
correctly for the PC hardware/software involved, can significantly
impact performance to the detriment of the response times (time to
deliver decodes) and excessive cpu load, made worse if on a very
busy band like 40m & 20m where 40+ decodes per period are now
common.
