Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Tarq57 on January 08, 2008, 02:32:06 AM
-
Usually when the definitions update, it takes about 5 - 7 sec, the sliding tab appears, and all is well.
Sometimes there is a pair of red/green arrows in the system tray (in the approx shape of the pictorial for the constellation Pisces) and mousing over them reveals only "Avast antivirus", right clicking on them does nothing. Then an update occurs which generally takes about 3-5 sec of actual download time, but 57 sec of total time. During those 57sec the computer is rather slow.
Is this normal? Couldn't find much reference to the process by searching.
-
It is normal. Processing the update was optimized so that it's quite fast on downloading (short files), but then it needs lots of processing time while applying the update.
If it leads to the desired result (ie. being up to date), then it's good, isn't it? ;)
-
Like I said, no problem. Just curious why some were fast, and some slowed the computer down.
Not about to start complaining!
Avast is stable, configurable, and all things good.
-
If it leads to the desired result (ie. being up to date), then it's good, isn't it? ;)
It's good. To be better (or the best) is another point.
Can't the update processing run at low priority, using less CPU resources? Or, at least, be an option into avast settings?
-
Tech, do you find similar symptoms during the updates that involve the red/green arrows, but not the other updates, then?
-
Indeed, I'm not monitoring avast updates that often.
It's set to update each 30 minutes (Pro version) and I run an script to update avast each connection is established.
-
There's a code in the updater that limits the CPU usage to 30% max. Doesn't it work in your case? I.e. when the update is taking place, does the updating process take more CPU than 30% or so? (or, if you're using a dual core machine, more than 15%)?
Cheers
Vlk
-
I've not checked the CPU while it's happening, but will do next time I notice it.
-
Vlk and kubecj, I presume you've seen other threads relating to near-lockup (on my system, anyway) while avast.setup is doing its thing but before the arrows icon kicks in? Most recently in the "wishlist", I think.
I haven't checked CPU usage, but typically I can't open Process Explorer (or much of anything else) until the icon does appear (at which point setup is apparently no longer active).
I think it was Tech who commented, and it makes sense, that the behavior is totally unexpected from a low-priority service. But it's enough of a nuisance that I'm about ready to throw in the towel and shut off auto-checks and just check manually once or twice a day.
Any ideas?
-
I can also confirm the updater ,uses excessive cpu for a period of time on w2000.Much more than 30%.The process seems to be using "below normal" priority rather than low?.However i think its something else other than the priority which causes this,as when process tamer lowers it to low priority ,it still uses 100% cpu.
[img=http://img201.imageshack.us/img201/8271/avastupsaterbb2.th.jpg] (http://img201.imageshack.us/my.php?image=avastupsaterbb2.jpg)
-
I can also confirm the updater ,uses excessive cpu for a period of time on w2000.
Does this occur with and without Process Tamer?
-
Yes it occurs without process tamer
If you check the screenshot ,process tamer hasnt actually started taming avast setup at that point but is merely showing the process.The scales icon in the tray area turn yellow when taming.
-
Yes it occurs without process tamer
If you check the screenshot ,process tamer hasnt actually started taming avast setup at that point but is merely showing the process.The scales icon in the tray area turn yellow when taming.
Well, hope the programmers could help...
-
Its not really a problem as i have the icons to show when avast updates ,so i just leave it do its thing.,and process tamer does lower its priority to low when needed ;)
It is just an observation that the updater is not as fine tuned as it ought to be (for me at least).Other than that i am very happy with avast and its protection.
-
Other than that i am very happy with avast and its protection.
Please, take a little time to see if your problem is not the same as this one:
http://forum.avast.com/index.php?topic=32556.msg272263#msg272263
-
I'm pretty sure that's not happening here, Tech.
I don't get the "failed update" red box. (Well, have once or twice, but seldom.)
The VPS updated to 080109-0 recently, with no slowdown, and no red/green arrows.
Yesterday it updated to (I think) 108, and there were red/green arrows, and a slowdown.
I'm of the same opinion as miscreant; I can certainly live with it. Just curious as to why some updates do this and others not.
-
Dang. Speak of the devil, it's just happened. No red/green arrows, just the red slide, and when clicked on, the error message pictured.
Will try a repair.
-
Will try a repair.
Please, post the last 200-250 lines of avast log: C:\Program Files\Alwil Software\Avast4\DATA\log\Setup.log
-
Here you go.(Sorry, uploaded the log twice. They're the same.)
-
There's a code in the updater that limits the CPU usage to 30% max. Doesn't it work in your case? I.e. when the update is taking place, does the updating process take more CPU than 30% or so? (or, if you're using a dual core machine, more than 15%)?
Cheers
Vlk
I uninstalled avast this evening (w2000 pro)and cleaned registry thouroughly etc.I then reinstalled avast ,and indeed the initial update of avast didnt go any higher than 29% (see screenshot).However updates after that initial first update reach up to 90% ,so something has altered after the initial update.
[img=http://img165.imageshack.us/img165/3135/avastfv7.th.jpg] (http://img165.imageshack.us/my.php?image=avastfv7.jpg)
-
Here you go.(Sorry, uploaded the log twice. They're the same.)
Seems ok... I see nothing wrong... strange, your avast seems updated.
-
Yep, it's updated. No problem, apart from (as said earlier) some updates are slow, and invoke the red/green arrows, and others are fast (Typically 7-20s) and don't invoke the red/green arrows.
Just want to know why.
-
Just want to know why.
Automatic updates run at silent mode.
Manual updates run with avast Update (Basic) > Details settings.
As far I know...
-
Automatic updates run at silent mode.
Manual updates run with avast Update (Basic) > Details settings.
As far I know...
I forget whether we've been talking about Home or Pro here, and quite likely this is one more area where there's no difference between them.
But (in Home, at least) there is a setting, under Updates, as to whether you want silent or showing progress. I imagine the latter is probably the default.
-
Let me make one thing clear: the CPU quota (30%) is only taking place for the automatic updates (i.e. these running on the background).
For user initiated updates, there's no restriction like this.
The rationale is that if the user invokes the update, we want to make it as fast as possible.
Cheers
Vlk