Re: time impact of the delta signature

> Il 26 febbraio 2019 alle 20.40 Denis Corbin <[email protected]> ha scritto:
> 
> Thus since that time, I enriched my thought with the function
> parameter not being a number but a real name and keep having on or
> more parameters as number. something like this:
> 
> - --delta sig:<function>:<num>[:...]
> 
> where function could be "log", "square_root", "cube_root", "linear",
> "fixed", while <num> would an integer number
> 
> - --delta sig:linear:10000
> 
> would correspond to your --delta sig:1:0.0001
> in other word block size being 1/10000 of file size
> 
> - --delta sig
> 
> would equal to
> 
> - --delta sig:2048
> which would be the same as:
> - -delta sig:fixed:2048
> 
> for backward compatibility
> 
> following your notation with
> - --delta sig:square:10
> 
> we would have
> 
> block-len-size = (S^2)/10
> 
> Doing that way is simpler to understand and simpler to sparse as well
> in dar. The underlying libdar API would also be more readable that way.
> 

Yes, this approach is surely more understandable, please consider also the possibility to specify a multiplicative factor for obataining, for instance,
block-len-size = 10*sqrt(S)

I.e. if you need integers input parameters, something like
--delta sig:<function>[:<multiplicativeFactor>[:<divisorFactor>]]

Andy