This thread is for discussions of Multithreading in VB.NET.

Volatility means a lot more than is described in the article. It doesn't just affect the variable which has the volatile modifed; it affects the whole memory model for sections of code involving access to that variable.

I agree that there's no use of volatile which can't be semantically achieved using locks, and indeed I generally prefer to use locks myself. However, there is a speed difference between acquiring a lock and just using a volatile variable - in a very few cases it might be significant. I'm surprised VB.NET doesn't have any way of specifying this.

See the volatility page of my C# threading article for more information.

Jon Skeet

Yes, but I decided not to go into detail since it's a vb.net article and you can't use it

As somewhat of an advanced "newbie" I have read many articles on Multithreading, and am at a loss

Do I need to have a delegate and call the delegate when I am using threading ?

 

Lets say I have a datatable with 5 million rows and I need to iterate through each row - grab some info , process that info (translate it) and then save it somewhere else. For example insert it inot a completely different database (and maybe even RDBMS - Architectur)

Now I currently for each row - but that takes a lot of time.

I would like to spawn a (Flexible Number of threads) to do the row processing - Will my For each move on as each thread runs. So I start Thread(1) will the next trigger, and I have a new row and can start thread(2) and so on. Also my Subroutine, must