Reply to thread

Message

<blockquote data-quote="breese" data-source="post: 1032638" data-attributes="member: 114299">With MP2 saving my DB files to my RamDrive it took almost 13hrs to complete&nbsp;So, here is an interesting fact.1st scan: Installed on SSD C: 6 and half hrs: DB file 3,536,668 kb2nd scan: Installed on Raid5 F: Over 24hrs: DB file&nbsp; 3,221,188 kb3rd scan: Installed on SSD C: configured to save DB to RamDrive R: 14hrs: DB file 3,218,692 kb&nbsp;While scans 2 and 3 are closer in size than 1, there appears to be a discrepency in size.No files were changed in my Music folder during any of these tests&nbsp;Idea:Why not import only what is needed on an initial scan likefile namedirectory&nbsp;Hold off on importing everything else until a user opens the Album, compair the info to the DB and update it.Speeds up initial scan, keeps the database to a minimum, and allows the system to auto update as the user open's / access's an album&nbsp;Thoughts?btw: the logs I uploaded are complete and Server Log does include the SQLDebug</blockquote>

[QUOTE="breese, post: 1032638, member: 114299"] With MP2 saving my DB files to my RamDrive it took almost 13hrs to complete So, here is an interesting fact. 1st scan: Installed on SSD C: 6 and half hrs: DB file 3,536,668 kb 2nd scan: Installed on Raid5 F: Over 24hrs: DB file 3,221,188 kb 3rd scan: Installed on SSD C: configured to save DB to RamDrive R: 14hrs: DB file 3,218,692 kb While scans 2 and 3 are closer in size than 1, there appears to be a discrepency in size. No files were changed in my Music folder during any of these tests Idea: Why not import only what is needed on an initial scan like file name directory Hold off on importing everything else until a user opens the Album, compair the info to the DB and update it. Speeds up initial scan, keeps the database to a minimum, and allows the system to auto update as the user open's / access's an album Thoughts? btw: the logs I uploaded are complete and Server Log does include the SQLDebug [/QUOTE]

Verification