|
#16
|
||||
|
||||
|
The internal naming is the name of the project i am replacing, for example addex is replacing srep and the internal name has many srep counterparts in it.
Addex is also heavily inspired from srep. And Tarz is also heavily inspired from Lolz. I am fixing Decompression because Tarz stdio decompression has some bugs. CLS should work. Let me explain how my multithreading works, the data is split in exactly as many threads as you request. For example if you have an input of 16GB and you request 16 threads. this automatically means you split the data in 16 parts of 1gb each, you create 16 sliding windows, 16 pairs of models and of course you will need exactly 16 threads to decompress the data. The reason i hard limited the threads to 16 is because of that because in the beginning i decied that even 8 will be alot. Tarz doesn't advertise encoding speed, however the decode speed is boosted when using multithreading because the load is decoded evenly. i don't yet have code to make this a block based encoding possible. something which lolz can do. there is a possibility to add this later. let me explain how ram works. each dictionary you create, needs * 10 the ram + number of block + 64mb for LRM. if you use 128mb dictionary and one thread, this means around 1600 mb of ram. to decompress this you need 128mb + 64mb for decoding. which if you ask me is quite efficient. it's highly assymetric.
__________________
My projects : Masked Compression, lzma2(xz) on Freearc, Zstd compressor for windows My optimizations : packjpg.exe, zstd, lzham, precomp-dev-0.45. |
| The Following User Says Thank You to panker1992 For This Useful Post: | ||
shazzla (27-10-2026) | ||
| Sponsored Links |
|
#17
|
|||
|
|||
|
RAM reqs are close to LZMA/LOLZ, usually it's always 10-11 times + some extra.
As for threads - yes, block-based mode is a must then. Otherwise repacking is usable only for the system which created it, running decompressing in current 16t mode on 4t machine would probably be a bad idea
|
|
#18
|
||||
|
||||
|
For the time being this project is a TEST only - Demo.
i am currently working on it, i am fixing decode stdio. what you guys in this forum can do to help me out is simple. Try it ..Combine it, let me know of the problems you see. so i can fix those. what i need is a sample in which lolz does better, if for example i havent added a model that can bypass Tanz in prediction. The block based Tarz will be a future addition which i also consider atm seriously. The sweat spot is 4 threads, it gives the best ratio and decompression speed ratio available ![]() as for lolz strings they will be gone soon i am rewriting this project clean. Silent Addition Fix, For decode on FA. Notice that Tarz is native to my project (Archiver) therefore the fix wasn't needed
__________________
My projects : Masked Compression, lzma2(xz) on Freearc, Zstd compressor for windows My optimizations : packjpg.exe, zstd, lzham, precomp-dev-0.45. Last edited by panker1992; 27-10-2026 at 13:43. |
|
#19
|
||||
|
||||
|
Tarz is now on version 1.0.3
With new features and fixes and some optimizations. I also decided to give you the default from the code directly to help the most advanced users. PS1. CLS for unpacking in 32Bit will be impossible. because in mtt1 it will kill the unarc.dll with ram overuse, i am awaiting for some feedback on this
__________________
My projects : Masked Compression, lzma2(xz) on Freearc, Zstd compressor for windows My optimizations : packjpg.exe, zstd, lzham, precomp-dev-0.45. Last edited by panker1992; Yesterday at 05:00. |
|
#20
|
|||
|
|||
|
Why not follow by Profrager's example and have a cls x86 with x64 exe handler?
|
|
#21
|
||||
|
||||
|
what i am expected to answer to this now ??
the tool was created to be used with RAM, why use a cls in 32 bit mode to further launch a 64 bit exe ?? BTW the question is good, the reason is quite simple. to make an exe use a DLL as a compatibility layer 2 things need to happen. either to use a 2 directional pipe with 4 mb cache and make it slower because data has to be copied from the exe to the dll. or the second is use memory share technology to pass the data as they are being written on the exe to the dll and as a consequence to the arc.exe which is a pain. Tarz is a tool i cherish and therefore i want it to be used properly. i also made archiver to replace FA which the community is so heavily bonded to and dont let die ![]() you will soon find out that Tarz is build-in to archiver as many other stuff already !
__________________
My projects : Masked Compression, lzma2(xz) on Freearc, Zstd compressor for windows My optimizations : packjpg.exe, zstd, lzham, precomp-dev-0.45. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| The Elder Scrolls V Skyrim *Incl HR Texture Pack + Update + DLC's* (2xDVD5 or 3xDVD5) | senseman | PC Games - CD/DVD Conversions | 66 | 31-12-2013 21:56 |
| Biathlon 2006 Problems... Please help! | RamGuy | General Gaming | 1 | 10-04-2006 04:23 |