Unless you have an analysis tool like SvchostAnalyser to see what processes are running under svchost.exe. as you can see it isn't easy to say it is avast because of svchost.exe activity.
It is easy to say when [b]svchost.exe [/b]activity drops back into its normal range as soon the update process is complete.