Compare commits
13 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
de8b6784d8 | ||
|
|
3f7969d8a2 | ||
|
|
1877038b93 | ||
|
|
2869f18bc5 | ||
|
|
c1b1f09d85 | ||
|
|
be43c340b2 | ||
|
|
71573c0149 | ||
|
|
9f5d97933b | ||
|
|
3ffc9d484b | ||
|
|
c9705d6cee | ||
|
|
7fbac2be16 | ||
|
|
b24afc1a24 | ||
|
|
95f35b14ac |
90
README.md
90
README.md
@@ -1,72 +1,30 @@
|
||||
# MultiPar
|
||||
|
||||
v1.3.2.0 is public
|
||||
### v1.3.2.3 is public
|
||||
|
||||
This is a beta version to test new encoder & decoder.
|
||||
I implemented a way of Cache Blocking for CPU's L3 cache optimization.
|
||||
It will calculate multiple blocks at once on multi-Core CPU.
|
||||
Old method calculated each block independently,
|
||||
and could not avail the advantage of shared memory.
|
||||
New method may use shared L3 cache more often, and will be fast on recent PCs.
|
||||
|
||||
Thanks [prdp19 and Slava46](https://github.com/Yutaka-Sawada/MultiPar/issues/47) for many tests.
|
||||
Thanks [Anime Tosho](https://github.com/Yutaka-Sawada/MultiPar/issues/21) for some idea and advice.
|
||||
Also, other users aided my development.
|
||||
Without their help, I could not perform this speed improvement.
|
||||
|
||||
While new version seems to be faster on most cases,
|
||||
it may happen to be slow for a few blocks.
|
||||
Though I don't know the speed on old PCs, it may not become slow.
|
||||
If you see a failure or strange result, please report the incident with ease.
|
||||
I will try to solve as possible as I can.
|
||||
|
||||
I adjusted CPU usage slider for CPUs with many Cores.
|
||||
Now, each position will set different number of threads always.
|
||||
Left most : 1/4 of CPU cores
|
||||
One from left : 2/4 of CPU cores
|
||||
Middle : 3/4 of CPU cores
|
||||
One from right : 4/4 of CPU cores, or use one less threads on CPU with 6 or more Cores.
|
||||
Right most : May use one more threads on CPU with 5 or less Cores.
|
||||
|
||||
I improved calculating hash of multiple source files.
|
||||
From my testing result, I changed default number of threads for NVMe SSD.
|
||||
When you use a raid-system or external drive, it cannot detect the drive type.
|
||||
If it fails to detect, it uses HDD mode by default.
|
||||
At MultiPar options, it's possible to change the setting manually.
|
||||
You may select one of them; HDD, SSD, or Fast SSD.
|
||||
Caution, you should not select SSD, if your using drive is HDD.
|
||||
This is a minor update version.
|
||||
Because some security vendors recognize MultiPar.exe's batch processing mode as stealth malware behavior,
|
||||
I removed the "/batch command" feature.
|
||||
Thanks [didamsko for reporting the problem and test](https://github.com/Yutaka-Sawada/MultiPar/issues/61).
|
||||
If someone wants batch operation, please use command-line version par2j64.exe instead of GUI version MultiPar.exe.
|
||||
|
||||
|
||||
[ Changes from 1.3.1.9 to 1.3.2.0 ]
|
||||
[ Changes from 1.3.2.2 to 1.3.2.3 ]
|
||||
|
||||
GUI update
|
||||
- Change
|
||||
- Fast SSD is selectable as file access mode.
|
||||
- Max number of log files was increased from 100 to 1000.
|
||||
- CPU usage slider was adjusted on CPU with 6 or more Cores.
|
||||
- Shadow of text over progress-bar becomes more smooth.
|
||||
|
||||
PAR2 client update
|
||||
- Change
|
||||
- Standard buffer size becomes double to decrease iteration.
|
||||
- Single byte error in a single slice file may be corrected.
|
||||
- Number of using threads was changed on CPU with 6 or more Cores.
|
||||
- Enabling GPU won't use additional threads on multi-core CPU.
|
||||
- Progress percent may move while writing blocks.
|
||||
|
||||
- Improvement
|
||||
- L3 cache optimization was implemented for multi-core CPU.
|
||||
Change
|
||||
I removed /batch command from MultiPar.exe.
|
||||
|
||||
|
||||
[ Hash value ]
|
||||
|
||||
MultiPar1320.zip
|
||||
MD5: 56524875BC77FD7A4E51A9E2C3F834CB
|
||||
SHA1: 245F3432DBCCAD335AEB2A70371EE57EFEF52CE7
|
||||
MultiPar1323.zip
|
||||
MD5: E66DD8773450C7E1A703EB5F2D935615
|
||||
SHA1: 362B4878B08463FAF9BC4CB551D68DAC0CA10575
|
||||
|
||||
MultiPar1320_setup.exe
|
||||
MD5: 5D0A51F48CDE8FCB0B87CC949BE84DD1
|
||||
SHA1: B727D5193697E8C0A2335DB8233874CBDAFDEE40
|
||||
MultiPar1323_setup.exe
|
||||
MD5: A1870227F3D40E7BCB94B9BE340A709A
|
||||
SHA1: 2DCB3D9E367B7DDAED7C950CD71F1538DF247F7D
|
||||
To install under "Program Files" or "Program Files (x86)" directory,
|
||||
you must start the installer with administrative privileges by selecting
|
||||
"Run as administrator" on right-click menu.
|
||||
@@ -77,17 +35,17 @@ you must start the installer with administrative privileges by selecting
|
||||
[GitHub](https://github.com/Yutaka-Sawada/MultiPar/releases) or
|
||||
[OneDrive](https://1drv.ms/u/s!AtGhNMUyvbWOaSo1n_R8awJ_hg0?e=4V0gXu).
|
||||
|
||||
MultiPar_par2j_1320.7z
|
||||
MD5: 5DBF880047D05BC2E8FE349DC6EC610C
|
||||
SHA1: 1D50EFE97A7812B6AF0090B83AAEE61BCBABD1ED
|
||||
MultiPar_par2j_1323.7z
|
||||
MD5: 587AF25EBB2ABF338FB1A07661E8A790
|
||||
SHA1: 6DD28E7BCF7AAC9B28EB3BA7CFFC14F67CC38D87
|
||||
|
||||
MultiPar_par1j_1318.7z
|
||||
MD5: F66285403BA0AD856BA6A8CCD922EBF5
|
||||
SHA1: 4CF5D819B16E60F1BBD82415D5F68CB46D3F53C3
|
||||
MultiPar_par1j_1322.7z
|
||||
MD5: E80BEB9BBFEAC709B0647E97580CD107
|
||||
SHA1: 84F51338C2AB1D8B9179319F20EB159F27D9FA2A
|
||||
|
||||
MultiPar_sfv_md5_1318.7z
|
||||
MD5: 4E6433808625C088E2773C961BBEBBD2
|
||||
SHA1: 68B54D178BA58637F63CC3E0CC656C96D4472A33
|
||||
MultiPar_sfv_md5_1322.7z
|
||||
MD5: 468540C08059987573404A860B43979A
|
||||
SHA1: 2B8AD55E1DC626A9F152554637B71EBE32F7C474
|
||||
|
||||
MultiPar_ShlExt_1320.7z
|
||||
MD5: C413655ABF85BCFF3D4B349BAAADC24B
|
||||
|
||||
Binary file not shown.
BIN
source/MultiPar_par1j_1322.7z
Normal file
BIN
source/MultiPar_par1j_1322.7z
Normal file
Binary file not shown.
Binary file not shown.
BIN
source/MultiPar_par2j_1323.7z
Normal file
BIN
source/MultiPar_par2j_1323.7z
Normal file
Binary file not shown.
Binary file not shown.
BIN
source/MultiPar_sfv_md5_1322.7z
Normal file
BIN
source/MultiPar_sfv_md5_1322.7z
Normal file
Binary file not shown.
Reference in New Issue
Block a user