Author Topic: [Resolved] Persistent Cache  (Read 3765 times)

0 Members and 1 Guest are viewing this topic.

Offline Para-Noid

  • Avast Evangelist
  • Starting Graphoman
  • ***
  • Posts: 6711
  • Trust only what you test yourself!
[Resolved] Persistent Cache
« on: January 29, 2011, 07:26:09 PM »
Is it me but it seems to take longer to "load up" the persistent cache with 5.1.889 than 5.0.667? The scans are getting faster but slowly. I know this is still v.5.x.xxx so it shouldn't matter. But it does seems slower filling the persistent cache.
« Last Edit: January 30, 2011, 01:21:59 AM by Para-Noid »
Dell Inspiron, Win10x64--HP Envy Win10x64--Both systems Avast Free v17.9.2322, Comodo Firewall v8.2 w/D+, MalwareBytes v3.0, OpenDNS, Super Anti-Spyware, Spyware Blaster, MCShield, Unchecky, Vivaldi Browser and, various browser security tools.

"Look before you leap!" Use online scanners before you click on any link.

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 86498
  • No support PMs thanks
Re: Persistent Cache
« Reply #1 on: January 29, 2011, 07:42:59 PM »
How do you know it is taking longer as there is no means of measuring it ?
It matters if you did a clean install of 5.1.889 as that would mean starting from scratch.

Once it is fully populated, which would take a few scans and or boots, it then wouldn't change as not all files are going to be added to the persistent cache. Once fully populated scan duration would generally level out if your settings don't change and there aren't large changes in your system.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.2.6003 (build 22.2.7013.717) UI 1.0.697/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Para-Noid

  • Avast Evangelist
  • Starting Graphoman
  • ***
  • Posts: 6711
  • Trust only what you test yourself!
Re: Persistent Cache
« Reply #2 on: January 29, 2011, 08:11:02 PM »
How do you know it is taking longer as there is no means of measuring it ?
It matters if you did a clean install of 5.1.889 as that would mean starting from scratch.

Once it is fully populated, which would take a few scans and or boots, it then wouldn't change as not all files are going to be added to the persistent cache. Once fully populated scan duration would generally level out if your settings don't change and there aren't large changes in your system.
That's what I thought. The way I determined "longer" is that the scan times are longer. I use the same settings and I did a complete uninstall of 5.1.667 then did a clean install of 5.1.889. And the scan times have leveled off at a little longer duration than before (about five minutes longer). It's no biggie but I was wondering if anyone else has noticed this.
Dell Inspiron, Win10x64--HP Envy Win10x64--Both systems Avast Free v17.9.2322, Comodo Firewall v8.2 w/D+, MalwareBytes v3.0, OpenDNS, Super Anti-Spyware, Spyware Blaster, MCShield, Unchecky, Vivaldi Browser and, various browser security tools.

"Look before you leap!" Use online scanners before you click on any link.

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 86498
  • No support PMs thanks
Re: Persistent Cache
« Reply #3 on: January 29, 2011, 10:23:14 PM »
You can't use scan duration to determine anything about the persistent cache.

Unless you have something that you can compare with, then again you can compare 5.0.677 (there is no 5.1.677), e.g. total files scanned and total GB scanned for the scans under 5.0.677 to what is being scanned now.

Whilst avast may also have added more packers to the latest 5.1 version, if you selected all packers in the full system scan then that would also make a difference.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.2.6003 (build 22.2.7013.717) UI 1.0.697/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Para-Noid

  • Avast Evangelist
  • Starting Graphoman
  • ***
  • Posts: 6711
  • Trust only what you test yourself!
Re: Persistent Cache
« Reply #4 on: January 30, 2011, 01:20:58 AM »
You can't use scan duration to determine anything about the persistent cache.

Unless you have something that you can compare with, then again you can compare 5.0.677 (there is no 5.1.677), e.g. total files scanned and total GB scanned for the scans under 5.0.677 to what is being scanned now.

Whilst avast may also have added more packers to the latest 5.1 version, if you selected all packers in the full system scan then that would also make a difference.
I meant 5.0.667. Resolved...thanks.
Dell Inspiron, Win10x64--HP Envy Win10x64--Both systems Avast Free v17.9.2322, Comodo Firewall v8.2 w/D+, MalwareBytes v3.0, OpenDNS, Super Anti-Spyware, Spyware Blaster, MCShield, Unchecky, Vivaldi Browser and, various browser security tools.

"Look before you leap!" Use online scanners before you click on any link.

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 86498
  • No support PMs thanks
Re: [Resolved] Persistent Cache
« Reply #5 on: January 30, 2011, 02:15:04 AM »
You're welcome.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 22.2.6003 (build 22.2.7013.717) UI 1.0.697/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security