Jump to content

parsprototem

Members
  • Posts

    3
  • Joined

  • Last visited

Reputation

0 Neutral
  1. You know, it might also be an interesting idea to add an option into the program that would capture some data (say, CPU + memory usage + disk access time for each disk being scanned) once every second, or every other second and submit it to Malwarebytes when the scan is complete. This way, we can have a better idea of where the bottlenecks are in the program across various systems.
  2. What about scanning multiple disks at once? I know that the disks will be the bottleneck in most systems, but I'm fairly certain that MBAM would be able to make very good use of multiple cores, in one way or another -- either scanning multiple disks at once, using parallel threads to do the signature matching on a file, maybe even some kind of heuristic scanning on files. Throwing extra computing power at the problem (detecting if a file is malware or not) should surely be able to yield some improvements in speed and accuracy. Again, I've been very happy with MBAM since I've been using it (I've even directed my friends to buy copies of it for the real-time protection), so I'm just trying to brainstorm some ways to tweak the performance a bit
  3. I've been using Malwarebytes for a while now to fix friends' computers when they get infected with malware. For a while though, I couldn't get it to run on my 64-bit system; today I looked at the website and saw that it does support 64-bit now, so I downloaded it and installed it on my own computer to run a quick scan. When I started the scan, I noticed that Malwarebytes only uses a single thread while scanning files. I've got an SSD, so I know that the disk is fast enough to feed multiple processors. What about adding multithreading support to the scanning part of Malwarebytes, so that those of us with multicore processors and a reasonably fast disk can get a speed boost? To avoid deadlocks when people have multicore processors + slow disks, you could keep a running speed "score" between all of the threads, and only add extra threads (up to the number of total cores/processors) when the current number of threads (starting at one) is pegging the core/processor it's on.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.