On 16/10/2014 21:12, Michael Black wrote:
Hi Mike,
Has any thought or attempt been given to multi-threading the decoding
process?
The decoding is almost exclusively Fortran code. Multi threading isn't
really the way Fortran code is parallelized (is that a word?), normally
a special
Hi Mike,
On 10/16/2014 4:12 PM, Michael Black wrote:
Has any thought or attempt been given to multi-threading the decoding
process?
To what end? Are you concerned about decoding speed? Have you looked
at the statistics in file 'timer.out', results from the built-in
execution profiler for
[mailto:j...@princeton.edu]
Sent: Friday, October 17, 2014 11:03 AM
To: WSJT software development
Subject: Re: [wsjt-devel] Threading
Hi Mike,
On 10/16/2014 4:12 PM, Michael Black wrote:
Has any thought or attempt been given to multi-threading the decoding
process?
To what end? Are you
Taylor [mailto:j...@princeton.edu]
Sent: Friday, October 17, 2014 11:55 AM
To: WSJT software development
Subject: Re: [wsjt-devel] Threading
Mike --
As a speed freak, you should pay attention to what timer.out can tell you.
As for the call flush(6) at line 171 of decoder.f90: it's there (inside
[mailto:j...@princeton.edu]
Sent: Friday, October 17, 2014 11:55 AM
To: WSJT software development
Subject: Re: [wsjt-devel] Threading
Mike --
As a speed freak, you should pay attention to what timer.out can tell you.
As for the call flush(6) at line 171 of decoder.f90: it's there (inside
the loop
On 10/17/2014 12:59 PM, Michael Black wrote:
Is showing up all at once a problem?
None of this is a problem, as far as I'm aware.
Is showing up all at once undesirable? Yes, if that means that the
first decode shows up later than it otherwise would have. The first
decode is always the one
Has any thought or attempt been given to multi-threading the decoding
process?
Mike W9MDB
--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls
