Reply to thread

Message

<blockquote data-quote="JohnH" data-source="post: 118973" data-attributes="member: 5139">5000 items eh? You should really consider providing only a filtered list, and if no filter is applied limit the list to say 100 items.With the current setup the number one speed improvement will be to use Control.BeginInvoke instead of Control.Invoke, this will allow the background thread to continue processing mp3s without waiting for the UI to update each item. Use ParameterizedThreadStart delegate to pass info over instead of the single set of module variables (songnamevar etc). Reading the tag info from each mp3 is what takes most time here, if you're planning on making this program anything useful you have to place the info gathered from mp3 files into persistant storage, like a file or db, this will save considerable time later when starting the program again, and later you only need to get info from new files for example. Anyway, you can't expect anything else than maxing cpu when doing processor intensive tasks, though you can lower the thread priority from default Normal. I don't think calling 'dosinglelist' in Catch block is a good call, if the cause of the Exception is not resolved you have a never-ending-loop. At least you should ask user for confirmation, to enable opting out.</blockquote>

[QUOTE="JohnH, post: 118973, member: 5139"] 5000 items eh? You should really consider providing only a filtered list, and if no filter is applied limit the list to say 100 items. With the current setup the number one speed improvement will be to use Control.BeginInvoke instead of Control.Invoke, this will allow the background thread to continue processing mp3s without waiting for the UI to update each item. Use ParameterizedThreadStart delegate to pass info over instead of the single set of module variables (songnamevar etc). Reading the tag info from each mp3 is what takes most time here, if you're planning on making this program anything useful you have to place the info gathered from mp3 files into persistant storage, like a file or db, this will save considerable time later when starting the program again, and later you only need to get info from new files for example. Anyway, you can't expect anything else than maxing cpu when doing processor intensive tasks, though you can lower the thread priority from default Normal. I don't think calling 'dosinglelist' in Catch block is a good call, if the cause of the Exception is not resolved you have a never-ending-loop. At least you should ask user for confirmation, to enable opting out. [/QUOTE]

Verification