Protection Engine for Cloud Services

 View Only

Performance with command line scanner vs .Net sample code?

  • 1.  Performance with command line scanner vs .Net sample code?

    Posted Feb 27, 2014 01:47 PM

    When scanning a 200M file, 64bit ssecls.exe takes 18 seconds, but a .Net console app using sample code in SDK takes about 1:36.

    When scanning a 1.6G file, ssecls finishes in 3 minutes or so, but .NET app gets ERR_RECIEVING_RESPONSE.

     

    I know the command line tool is a 64bit C code, so it's probably more efficient.  In my case, I need some pre/post processing of the files, so can't use command line directly.  Is there a way to improve the .NET way?  Or is repeatedly launching command line tool from .NET code a good idea?

    Thanks.