CompactGUI icon indicating copy to clipboard operation
CompactGUI copied to clipboard

Thread limit does not appear to be enforced.

Open Oroborius opened this issue 7 months ago • 4 comments

Setting the thread limit in settings doesn't actually do anything it would seem. Even if limiting to 1-8 threads no dice.

On a 7950X3D, Limiting to 1 thread, still at 100% usage when using LZX.

Oroborius avatar May 04 '25 14:05 Oroborius

Does the speed of the compression change? I can't replicate this on my end. My CPU hits 50% usage, but that's averaged out - it only uses one thread at a time, but I think that thread can be sent to any of the cores depending on what's free.

If I add an intentional 1 second delay to each task, it does show only one item being processed at a time

Iridium-IO avatar May 22 '25 12:05 Iridium-IO

Does the speed of the compression change? I can't replicate this on my end. My CPU hits 50% usage, but that's averaged out - it only uses one thread at a time, but I think that thread can be sent to any of the cores depending on what's free.

If I add an intentional 1 second delay to each task, it does show only one item being processed at a time

I hadn't checked whether or not the speed had changed however if it did it wasn't significant enough for me to notice, I was attempting to use it to compress about 1.8TB of data.

In any case maybe it's just an issue with the tool from Windows? That was tested on 23H2. Maybe it's different on 10 (21H2) or 11 (24H2).

Oroborius avatar May 26 '25 05:05 Oroborius

Hmm it shouldn't be different, I don't think the underlying functions changed between 10 and 11. Can you try again compressing a smaller folder and time it instead? there should be a noticeable difference between 1 thread and all threads

Iridium-IO avatar May 30 '25 07:05 Iridium-IO

Can you try again compressing a smaller folder and time it instead?

Win10 21H2 (build 19044.1288). 28-thread CPU. RAM disk (to eliminate the storage speed factor). LZX algo. Two folders: one with 56 files (made it twice the thread count to saturate the CPU, and just in case), and a second one with just 1 file (about the same size as all files above combined - simulates a game with a chunky resource archive in almost the size of the whole game folder). 0 files were skipped, ofc. Dunno whether that post will be helpful, but it never hurts to add a bit more info.

  • CompactGUI v3.8. 56 files in the folder. 0 (auto) threads: 01m20s, 100% CPU usage (all threads were at 100%). 1 thread: 03m55s, ~30% CPU usage (6 threads were close to 100%, a few more at about half load, the rest were at 0%).

  • CompactGUI v3.8. 1 file in the folder. 0 (auto) threads: 01m59s, ~30% CPU usage (6 threads were close to 100%, a few more at about half load, the rest were at 0%). 1 thread: 02m00s, ~30% CPU usage (6 threads were close to 100%, a few more at about half load, the rest were at 0%).

  • CompactGUI v4.0 beta 5. 56 files in the folder. 0 (auto) threads: 01m22s, 100% CPU usage (all threads were at 100%). 1 thread: 03m58s, ~30% CPU usage (6 threads were close to 100%, a few more at about half load, the rest were at 0%).

  • CompactGUI v4.0 beta 5. 1 file in the folder. 0 (auto) threads: 02m02s, ~30% CPU usage (6 threads were close to 100%, a few more at about half load, the rest were at 0%). 1 thread: 02m03s, ~30% CPU usage (6 threads were close to 100%, a few more at about half load, the rest were at 0%).

Vitaliuz avatar Jun 18 '25 15:06 Vitaliuz