Todays systems are pretty fast, like using NVMe drives, fast CPU's etc.
However, it seems UE doesn't fully utilize all the available resources. For example, if something unrars, no files are getting saved.
The unrar is also not super fast (130MB/sec disk use, 40% CPU usage in my case).
Are there any plans for multi-threading the operations?
Multi-Threaded operation possible?
Re: Multi-Threaded operation possible?
Unrar is third party code so I cannot do much about it.
Downloading article bodies is asynchronous, but there is a single thread to process save and unrar - to simplify synchronization and normalize disk load.
With 40% cpu it would allow maybe 2-3 unrar processes, but making them a separate process is not trivial.
Then probably there would be need to differentiate between mechanical and SSD drives since e.g. when two processes would write 130MB/s into mechanical drive everything will be slow.
Downloading article bodies is asynchronous, but there is a single thread to process save and unrar - to simplify synchronization and normalize disk load.
With 40% cpu it would allow maybe 2-3 unrar processes, but making them a separate process is not trivial.
Then probably there would be need to differentiate between mechanical and SSD drives since e.g. when two processes would write 130MB/s into mechanical drive everything will be slow.
Re: Multi-Threaded operation possible?
If you want you can run several usenet explorer instances.
Just create a UE.exe shortcut and add the database path to the shortcut "Target" edit control.
So as long as your hardware allows you can double or triple performance.
Just create a UE.exe shortcut and add the database path to the shortcut "Target" edit control.
So as long as your hardware allows you can double or triple performance.