C# async/await or background worker?
I cant find a comparision they both sound similiar.. whats the best strategy for paralel or async tasks?
As far as I've met them (not by definition, but by experience): Being parallel means to optimize for bites, like taking equal pieces of the process for some threads available, so multiple cores do it faster. However, if there are no further threads available, it still works as a simple sync process. For example there is the Collection::ForEach method, you call it, and your code will not continue, until the loop is ended, and all elements are used by the loop. At the same time, you do not need to know, if the elements are used on the same thread, or in what order, so it can be parallel too, but still a sync call - you wait for it. Asynchronous calls let the code run next without waiting the end of the task, usually providing an object to monitor the async task, named FutureTask or the likes. Async calls are typically scehuled tasks. However, if the main thread handles the scheduler, it's still sync from the point of view of the main thread, but seems async when you request the task to happen some time later. I mean, you register the task for later, and instead of waiting for it the code continues the execution. Async is used in parallel optimization, but not the other way around. A call/process can be both parallel and async, either, or neither.
Thanks a lot for the explanation..what about Background worker ? Is it same as async& await or there are situations where you prefer one over other?
Read the following article. It explains it through examples and in a logical way, also mentioning BackgroundWorker's: https://msdn.microsoft.com/library/hh191443(vs.110).aspx
Awesome thank you so much
Your welcome ;)
Application RAM usage
About Java McQ
How to split a string ,containing two or more integers seperated by comma, into two or more integers.