Printable View
.NET Framework 101 :D
Any .NET app is compiled to an intermediate code and then when the application is ran the first time on any machine, the .NET Framework process compiles that intermediate code to be optimized for the machine it's running on.
My question comes now..! Does that mean that it can take full advantage of Multi Processor/Multi Core CPUs automatically..?
Cheers :)
I believe so, but only if you are making efficient use of threading in your application by design.
I'm not sure how much you already know about multi-threading but the Articles -> Advanced .NET link in my signature leads to series of advanced .NET topics including Managed Threading and Asynchronous Programming, which you will need to use copiously to take advantage of multiple processors. If you design your app to use a single thread then the Framework won't change that. It couldn't possibly because it would have no idea how everything needed to be synchronised. Note also that use of multiple threads can, in certain instances, slow down an app when running on a single processor system. The types of apps that benefit most from multi-threading are those that have long-running operations that don't necessarily prevent the user or the app doing something else at the same time. If your app doesn't have those sorts of operations then multi-threading will not be of any benefit.
Thanks both. I am writing an app which will be deployed on a server where multi processor is a requirement (other apps running requires it). So if I am not going to use the full potential of the server's processor cores than no point migrating my app to the new server requirements.
Currently its in VB6 where I would not prefer going to threaded route. Its mostly used behind the scene data processing and manipulation so I think it would best benefit from using all processors where I can kick in as many threads as number of processors and process that many times more data.