it is about cls srep by Profrager

[ZakirAhmad]

is it possible with cls srep by Profrager to avoid creating srep temp file on disk. I mean i only want to use memory (ram) for decompression.

[shazzla]

Use Razor's cls-srep. it doesnt create tmp file.

[-NORO-]

Yes it is possible , just remove srepinit or srepinside function from your .iss
if not SrepInit(AddBackSlash(ExpandConstant('{app}')),512 ,0) then
ISDoneError := True;

However its buggy , for example if decompression memory is 6 gb and if you have only 4 gb free ram, it will write 4 gb temp files in ram memory and after that crashes and will not write left 2 gb into disk
Unfortunately i didnt manage to fix this issue.
Razor's cls-srep is maybe a little bit slower than Profrager's one but it works great

[FitGirl]

is it possible with cls srep by Profrager to avoid creating srep temp file on disk. I mean i only want to use memory (ram) for decompression.
Never do that for public. Only if you make conversions for yourself and can be sure you will always have enough RAM for decompression.

[artag]

Never do that for public. Only if you make conversions for yourself and can be sure you will always have enough RAM for decompression.

Correct, depending on how much data you fed to srep, decompression memory can be very high (more than 10GB). Are you sure you have enough?

You can also play with l and c settings to see if that helps with memory requirements, but you may lose compression. Do some testings.

Good luck

[ZakirAhmad]

I compressed mad max from 32 gb to 4.83gb using ztool srep lolz but while extracting it is creating srep virtual memory of 20gb while Fitgirls create only 6GB of virtual memory. please help.

[elit]

I compressed mad max from 32 gb to 4.83gb using ztool srep lolz but while extracting it is creating srep virtual memory of 20gb while Fitgirls create only 6GB of virtual memory. please help.

This depend on ":mem{##}g" parameter of srep that you specify during compression. It will use RAM up to that much(during decompression) and the rest will go to srep-tmp file. If you want to avoid tmp completely dont specify this parameter, but decompression will fail if it need more than you have. To control memory(and in turn compression), use "l" parameter(not "c" as was suggested, although that one affect to some degree as well), like ":l1k" for example. "l" parameter is the key here. Then there are other options like limiting max size of match stored etc., but I think this is enough.

[ZakirAhmad]

This depend on ":mem{##}g" parameter of srep that you specify during compression. It will use RAM up to that much(during decompression) and the rest will go to srep-tmp file. If you want to avoid tmp completely dont specify this parameter, but decompression will fail if it need more than you have. To control memory(and in turn compression), use "l" parameter(not "c" as was suggested, although that one affect to some degree as well), like ":l1k" for example. "l" parameter is the key here. Then there are other options like limiting max size of match stored etc., but I think this is enough.

i tried the mem parameter of srep but it seems the srepinit fuxtion of isdone is overriding my settings of memory usage by step. is their a way to write memory like 80%-512mb in srepinit fun of isdone.

[78372]

Just don't use srepinit

[ZakirAhmad]

Just don't use srepinit

i guess srepinit creates cls.ini for srep but if i dont use it setup crashes.

[ZakirAhmad]

i have no idea why srep temp keeps on grow bigger and how fitgirl in first repack of mad max limited to 5.5gb.
however i do known in first repack of madmax she used cls srep by Profrager without exe while in second repack of madmax she used cls srep with cls srep x64.exe and cls srep x86.exe

[78372]

i have no idea why srep temp keeps on grow bigger and how fitgirl in first repack of mad max limited to 5.5gb.
however i do known in first repack of madmax she used cls srep by Profrager without exe while in second repack of madmax she used cls srep with cls srep x64.exe and cls srep x86.exe

While installing, go to temp folder to see her cls.ini to know her trick for less temps

[ZakirAhmad]

the cls.ini in her tmp folder contains mem = 484b, irrespective of this her srep uses my full ram as if memory is given in percentage.

[ZakirAhmad]

i tried to use parameters like d1g and a0 while compressing with srep but still srep need 15gb of virtual memory.
i wonder how fitgirl archieved mad max.

[doofoo24]

if you installing the game on ssd see total host writes before and after th setup and see the total amount of gb written to the ssd...
if there no temp file as you say then the differents should be the game size...
or use srep 3.93a and see the decomprssion ram after srep finishes

[ZakirAhmad]

if you installing the game on ssd see total host writes before and after th setup and see the total amount of gb written to the ssd...
if there no temp file as you say then the differents should be the game size...
or use srep 3.93a and see the decomprssion ram after srep finishes

I tried different version of srep to compress the game but still it needs around 15gb of ram to decompress how the repwck of fitgirl which i am heaving needs only 6gb of ram.
that means if i put limit of ram to 2gb, it will create a temp file of 13gb.
any idea how can i optimize srep ram usage during decompression.

[doofoo24]

well srep is the same as the one from ProFrager (the new ver) if you have enough RAM like 21.5gb it still well create 5gb of temp file...
game size 32gb but as you see in the picture before and after there is 37gb of data has been written to the drive and the memory usage for srep around 21341mb

[ZakirAhmad]

well the second repack of fitgirl uses that much ram but the first repack the 4.1gb one uses only 7gb and in this repack she has uses cls-srep.dll 86kb.
not this cls

[Jiva newstone]

@ZakirAhmad
hey you should add memory expection in srep like this srep:mem256mb+lolz
it means only 256mb will need for memory and remaining will go to the virtual file

[ZakirAhmad]

the idea was to limit tmp file creation and minimum memory usage while maintaining the sMe compression ratio and i did this by using parameter m2f. it only needs 2.2gb of ram and has almost sMe ratio.