As all high-level-language-apostles say, it shouldn’t be visible (but we, low-level-defenders, know, that all the C++ crap around wx-widgets or any other portable GUI-framework could cause some speed decrease).
But, in the case of avast, there’s quite low interaction between the gui and the scanning core, so the slowdown will be really small and neglectable, if not even invisible… so the problem will be probably in the switches used (scan fullfiles, packer sets etc.). specify the same scanning properties from the cmdline and the speed should be similar.
Thank you for your reply. Since that reply I have done two separate sets of comparable tests (in that the numbers of items and total sizes scanned were identical). In both cases the GUI method has taken some 40% longer than using the Console.
I would still like to know if “daily” updates can be done from the Command Line and, if so, which command to try?
My regards
Added:
I just tried a Quick scan on one of the above tests using the GUI and that was faster than using the Console, but I have no idea if my Console automatically uses Quick, Standard or Thorough (perhaps there is a log to tell me).