Configuration
- Keka version: [e.g. 1.2.11 (4493)]
- macOS version: [e.g. 10.15.7 (19H524)]
Describe the bug
Keka use only one cpu core
If your use console zstd with -T0 -4 argument, we see very fast compression.
2021-03-05 14:59:51.367 DEV: Path set as unavailable: /Users/ilya/VirtualBoxVMs.tar.zst
2021-03-05 14:59:51.369 DEV: Checking tasks queue
2021-03-05 14:59:51.395 DEV: Starting queued task
2021-03-05 14:59:51.396 DEV: OS: Версия 10.15.7 (Выпуск 19H524)
2021-03-05 14:59:51.396 DEV: Keka: v1.2.11-r4493 (WEB) (Sandboxed) (ru)
2021-03-05 14:59:51.396 DEV: Binary used: kekazstd
2021-03-05 14:59:51.396 DEV: Arguments: (
"-4",
"-T0",
"-o",
"/Users/ilya/VirtualBoxVMs.tar.zst",
"/Users/ilya/VirtualBoxVMs.tar"
)
2021-03-05 14:59:51.420 READER:
Read : 0 / 88615 MB ==> 33%
2021-03-05 14:59:51.587 READER:
Read : 25 / 88615 MB ==> 41%
2021-03-05 14:59:51.754 READER:
Read : 54 / 88615 MB ==> 64%
2021-03-05 14:59:51.871 DEV: Showing delayed tasks
2021-03-05 14:59:51.921 READER:
Read : 95 / 88615 MB ==> 77%
2021-03-05 14:59:52.087 READER:
Read : 133 / 88615 MB ==> 62%
2021-03-05 14:59:52.254 READER:
Read : 167 / 88615 MB ==> 55%
2021-03-05 14:59:52.422 READER:
Read : 192 / 88615 MB ==> 51%
2021-03-05 14:59:52.589 READER:
Read : 219 / 88615 MB ==> 48%
2021-03-05 14:59:52.756 READER:
Read : 246 / 88615 MB ==> 45%
2021-03-05 14:59:52.922 READER:
Read : 271 / 88615 MB ==> 43%
2021-03-05 14:59:53.089 READER:
Read : 293 / 88615 MB ==> 42%
2021-03-05 14:59:53.256 READER:
Read : 320 / 88615 MB ==> 40%
2021-03-05 14:59:53.424 READER:
Read : 355 / 88615 MB ==> 39%
2021-03-05 14:59:53.591 READER:
Read : 394 / 88615 MB ==> 36%
2021-03-05 14:59:53.758 READER:
Read : 416 / 88615 MB ==> 36%
2021-03-05 14:59:53.925 READER:
Read : 444 / 88615 MB ==> 36%
2021-03-05 14:59:54.094 READER:
Read : 463 / 88615 MB ==> 36%
2021-03-05 14:59:54.260 READER:
Read : 484 / 88615 MB ==> 36%
2021-03-05 14:59:54.427 READER:
Read : 509 / 88615 MB ==> 35%
2021-03-05 14:59:54.594 READER:
Read : 527 / 88615 MB ==> 35%
2021-03-05 14:59:54.761 READER:
Read : 551 / 88615 MB ==> 35%
2021-03-05 14:59:54.928 READER:
Read : 633 / 88615 MB ==> 31%
2021-03-05 14:59:55.095 READER:
Read : 771 / 88615 MB ==> 26%
2021-03-05 14:59:55.262 READER:
Read : 809 / 88615 MB ==> 26%
2021-03-05 14:59:55.430 READER:
To Reproduce
Steps to reproduce the behavior:
1.Open keka
2.Create zstd archive
Expected behavior
Very fast compression with multicore
Screenshots

Configuration
Describe the bug
Keka use only one cpu core
If your use console zstd with -T0 -4 argument, we see very fast compression.
To Reproduce
Steps to reproduce the behavior:
1.Open keka
2.Create zstd archive
Expected behavior
Very fast compression with multicore
Screenshots