Jump to content

Multithread and multiple discs.

Recommended Posts

I read a post that says MBAM will be multithreaded back in 2009 but I do not see it using multiple threads on my 4770K. I see it cap at a single thread and my Sandisk Extreme Pro drops in speed. It will also drop well below the speed of a full core/thread but that's obviously due to the SSD not keeping up at those given moments. So is multithreaded scans not even available yet? even though you were working on it in 2009?


Also when will you scan multiple drives at once? I have yet to hear a single AV/AM scan several drives at once or send Q32 depth requests....why keep requests to a single drive and to a single thread in regards to CPU and HDD. The CPUs sit so freakin ideal these days doing scan because SSDs/HDDs/CPUs are not being properly utilized.


Why are these features not implemented like 5 years ago?

multithread CPU scanning

high Q depth requests (gets ride of the 4K issue)

scan all drives at once


These seem basic common sense to me and I just wanted to know why they haven't been done yet...some of them are even easy like scanning several drives at once and high Q depth -_-

Link to post
Share on other sites

Still single-threaded.  I believe (though I could be mistaken) that other items have had higher priority.  If @bdubrow happens to read this, she could comment further on the present state and what future plans can be spoken of.  Once that changes, multiple concurrent drive scanning becomes a possibility.


I don't know what you mean by "high Q depth requests" so I don't know what to say there.

Link to post
Share on other sites

How many request are sent at once. SSDs are much much faster when you have Q32 4K requests or even multithreaded 512K requests. 


Queue depth is the number of I/O requests (SCSI commands) that can be queued at one time on a storage controller. Each I/O request from the host's initiator HBA to the storage controller's target adapter consumes aqueue entry


So here is my SSD



See the difference for 4K when it has a queue depth of 32? NVMe will have a much higher depth limit. The intel 750 can do 128 or more IIRC. normal drives are limited to 32 depth.


The ability to queue that deep would do wonders of making it faster along with allowing multiple threads.


It honestly is disappointing if mutithread support was being worked on 6 years ago and yet has not been added :/

Link to post
Share on other sites

 I don't see an edit button for posts so sorry for double post.


I just wanted to say sorry for not explaining well with the terms. I understand how it works but I rarely use these terms so I might be off a bit in using the right words plus I am rushed becuase I keep forgetting to post this and I have a dead line in an hour and 45 mins  :(

Link to post
Share on other sites

We don't allow editing for junior members.  They sometimes say something and after it gets answered, it turns into something that embarrasses a sailor AFTER he's been carousing all night.


I'm glad you did explain, as some people would call me a names for not knowing everything and daring to answer a post.


I don't know the answer to your question, and doubt that the product manager would either.  That's a deep down dev question.  If that is part of a SCSI construct, I also don't know if it would translate to the kind of disks that most people use.  PATA and SATA are the norm, while IDE is fading away, SCSI is pretty much high-end business, and ESDI (remember that one?) is long gone.  We would also have to be able to have code that would tailor disk requests to 64 or 32 bit OS versions, and deal with everything from XP to Windows 10.  That might take some serious work to be able to do that bug-free.  Let's see if the PM comes back with anything.

Link to post
Share on other sites

queue depth exists for everything. That was just an explanation in a server sense. The link to dropbox shows my Sandisk Extreme Pro SATA 3 SSD which is a high end consumer SSD. You can clearly see Q32 4K 9-18 times faster than Q1 4K (standard 4K above the Q32) You get similiar result even with a cheap Samsung 830 (version before the EVOs)

Link to post
Share on other sites

crap....setting a depth of a que works on any OS and the depth should be something easy to control...granted I know very little about actual coding but all your doing really is making a batch request instead of individual requests. It allows the controller in ANY HDD/SSD or what what you request everything at once in a sequential manner (I think...I might be getting some of this wrong  but the jist should be right.) 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
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.