View Single Post
  #8  
Old 18-02-2018, 10:04
ZakirAhmad ZakirAhmad is offline
Registered User
 
Join Date: Sep 2015
Location: Kmr
Posts: 290
Thanks: 56
Thanked 58 Times in 37 Posts
ZakirAhmad is on a distinguished road
Quote:
Originally Posted by elit View Post
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.
Reply With Quote