|
I am running WSJT-X V2.2.2 on a Win10 machine using I7-8565 CPU with variable speed and 16 GB memory. Attached shows the CPU usage for a crowed band of 30 to 40 decodes.
There are no other compute intensive tasks, With monitoring stopped the CPU usage is about 10%. The decoding task is peaking 60% every 15 secs. However every few minutes there is a heavy task which adds a pedestal CPU usage of 65% for 5 to 8 secs. The decoding running on top of this peaks nearly 100% on this machine. This pedesal task has been growing over time. I believe it is related to handling the all.txt file which is growing all the time and has approached a file size of 1.2 GB.
If I delete this file it would start all over again but I would lose my QSO history. Would it be possible to store only data relevant for my station in order to substantially limit the amount of stored data? It should also be possible to clean up this file to delete everything not related to my call.
Any ideas?
73,
Hans, DK1WB
|
|
|
Correct me if I'm wrong but the logged QSO's are in the log file in addition to the ALL file. So you should still have the QSO history even if you clear the ALL file. Is that not correct?
|
|
|
neil_zampella <neilz@...>
Stop WSJT-X, rename the all.txt to something like
2019-2020_all.txt, then restart WSJT-X.
Neil, KN3ILZ
toggle quoted message
Show quoted text
I am running WSJT-X V2.2.2 on a Win10 machine using I7-8565 CPU
with variable speed and 16 GB memory. Attached shows the CPU
usage for a crowed band of 30 to 40 decodes.
There are no other compute intensive tasks, With monitoring
stopped the CPU usage is about 10%. The decoding task is peaking
60% every 15 secs. However every few minutes there is a heavy
task which adds a pedestal CPU usage of 65% for 5 to 8 secs. The
decoding running on top of this peaks nearly 100% on this
machine. This pedesal task has been growing over time. I believe
it is related to handling the all.txt file which is growing all
the time and has approached a file size of 1.2 GB.
If I delete this file it would start all over again but I would
lose my QSO history. Would it be possible to store only data
relevant for my station in order to substantially limit the
amount of stored data? It should also be possible to clean up
this file to delete everything not related to my call.
Any ideas?
73,
Hans, DK1WB
Attachments:
|
|
|
On 24/01/2021 22:02, dk1wb@... wrote: I am running WSJT-X V2.2.2 on a Win10 machine using I7-8565 CPU with variable speed and 16 GB memory. Attached shows the CPU usage for a crowed band of 30 to 40 decodes.
There are no other compute intensive tasks, With monitoring stopped the CPU usage is about 10%. The decoding task is peaking 60% every 15 secs. However every few minutes there is a heavy task which adds a pedestal CPU usage of 65% for 5 to 8 secs. The decoding running on top of this peaks nearly 100% on this machine. This pedesal task has been growing over time. I believe it is related to handling the all.txt file which is growing all the time and has approached a file size of 1.2 GB.
If I delete this file it would start all over again but I would lose my QSO history. Would it be possible to store only data relevant for my station in order to substantially limit the amount of stored data? It should also be possible to clean up this file to delete everything not related to my call.
Any ideas?
73,
Hans, DK1WB
Why don't you just rename your all.txt file and then you can keep it for future reference and use a smaller new file in the future? 73 Roger GW4HZA
|
|
|
Jim Shorney
Better yet, archive it as a ZIP file. 73 -Jim NU0C On Sun, 24 Jan 2021 16:17:04 -0600 "neil_zampella" <neilz@...> wrote: Stop WSJT-X, rename the all.txt to something like 2019-2020_all.txt,
then restart WSJT-X.
Neil, KN3ILZ
On 1/24/2021 4:02 PM, dk1wb@... wrote:
I am running WSJT-X V2.2.2 on a Win10 machine using I7-8565 CPU with
variable speed and 16 GB memory. Attached shows the CPU usage for a
crowed band of 30 to 40 decodes.
There are no other compute intensive tasks, With monitoring stopped
the CPU usage is about 10%. The decoding task is peaking 60% every 15
secs. However every few minutes there is a heavy task which adds a
pedestal CPU usage of 65% for 5 to 8 secs. The decoding running on top
of this peaks nearly 100% on this machine. This pedesal task has been
growing over time. I believe it is related to handling the all.txt
file which is growing all the time and has approached a file size of
1.2 GB.
If I delete this file it would start all over again but I would lose
my QSO history. Would it be possible to store only data relevant for
my station in order to substantially limit the amount of stored data?
It should also be possible to clean up this file to delete everything
not related to my call.
Any ideas?
73,
Hans, DK1WB
Attachments:
* IMG_8324.jpg <https://WSJTX.groups.io/g/main/attachment/21054/0>
|
|
|
>If I delete this file it would start all over again but I would lose my QSO history. Would it be possible to store only data relevant for my station in order to substantially limit the amount of stored data? It should also be possible to clean up this file to delete everything not related to my call.
Any ideas? Hans,
Do you mean that you want to keep also knowledge which messages were exchanged with you during each call or only logging information?
If the first, then renaming ALL.txt and zipping it is most efficient storing method. If the second, then ALL.txt is not relevant as all logging information is in wsjtx_log.adi file.
73, Reino OH3mA
|
|
|
Thanks Reino.
I am not sure anymore, if the large CPU load every couple of minutes is due the the all.txt file. Do see similar things?
73,
Hans, DK1WB
Am 2021-01-25 12:45, schrieb Reino Talarmo:
toggle quoted message
Show quoted text
>If I delete this file it would start all over again but I would lose my QSO history. Would it be possible to store only data relevant for my station in order to substantially limit the amount of stored data? It should also be possible to clean up this file to delete everything not related to my call.
Any ideas?
Hans,
Do you mean that you want to keep also knowledge which messages were exchanged with you during each call or only logging information?
If the first, then renaming ALL.txt and zipping it is most efficient storing method. If the second, then ALL.txt is not relevant as all logging information is in wsjtx_log.adi file.
73, Reino OH3mA
|
|
|
Bill Somerville
Hi Hans,
there should be no spike in CPU load
related to writing to ALL.TXT that is correlated to the size of
ALL.TXT. WSJT-X simply appends to ALL.TXT which should be a
costant time complexity, i.e. not proportional to the file size.
What might be happening is that anti-virus software may be
scanning the whole file every time it sees it being modified, that
could lead to CPU load being dependent of the size of the file.
Adding an exception to your AV real-time scanning for the ALL.TXT
file would verify if that was the cause.
73
Bill
G4WJS.
toggle quoted message
Show quoted text
Thanks Reino.
I am not sure anymore, if the large CPU load every couple of
minutes is due the the all.txt file. Do see similar things?
73,
Hans, DK1WB
Am 2021-01-25 12:45, schrieb Reino Talarmo:
>If I delete this file it
would start all over again but I would lose my QSO
history. Would it be possible to store only
data relevant for my station in order to substantially
limit the amount of stored data? It should also be
possible to clean up this file to delete everything not
related to my call.
Any ideas?
Hans,
Do you mean that you want to keep also knowledge which
messages were exchanged with you during each call or
only logging information?
If the first, then renaming ALL.txt and zipping it is
most efficient storing method. If the second, then
ALL.txt is not relevant as all logging information is
in wsjtx_log.adi file.
73, Reino OH3mA
|
|
|
