Thread Priority and Process Priority

In our walk of life almost of us have done some amount of "multithreading" programming sometime or other and also there are few cases when we have set the "ThreadPrority" level to make sure that the thread gets more/less CPU.

If we look at the "ThreadPriority" enum, we can see there are 5 values ( AboveNormal, BelowNormal,Normal,Highest and Lowest ), a thread’s Priority property determines how much execution time it gets relative to other active threads in the same process, so does that mean if we set the "ThreadPriority" of a thread as "Highest" then the thread will run almost like a realtime application ?

Well NO, setting a thread’s priority to "Highest" doesn’t mean it can perform real-time work, because it’s still limited by the application’s process priority( read "BasePriority"). The Process class has a property named "BasePriority" returns a number which indicates the priority level at which the process is running.

Let us have a look at the internal mechanism, how exactly windows OS work ? the Windows 32-bit operating systems schedule threads using 32 priority levels, numbered from 0 to 31. The highest-numbered thread is processed first. As threads wait to be processed, their priority levels are increased. The base application priority determines the priority level at which threads begin.

For example if a process is running with a "BasePriority" Normal(which is the default value ) and we set the "ThreadPriority" of a thread as "Highest" then the priority level of the thread will be 9( visit this link [http://msdn2.microsoft.com/en-us/library/ms685100.aspx] to see all the combination of Process.BasePriority and Thread.ThreadPriority, it shows the scheduling priority level with respect to the Process.BasePriority and Thread.ThreadPriority ), so if there is any other thread which has higher level ( > 9 in this context), that will run first.

So, to get the expected behavior( say we want to run an application almost like a realtime application which should consume most CPU and there should not be any preempt on this thread)setting the "ThreadProperty" will not be enough, we must set the "Process.BasePriority"accordingly. To set the BasePriority of a Process we have take help of the "PriorityClass" property of the Process class( since Process.BasePriority is a readonly property ).

Sample code:
System.Diagnostics.Process p = System.Diagnostics.Process.GetCurrentProcess(); p.PriorityClass = System.Diagnostics.ProcessPriorityClass.High;

Alternatively we can do the above thru TaskManager also.

Note: As per MSDN documentation we must not set the ProcessPriority as "Realtme" cause that will preempt all other processes( even OS process )which will lead to a machine hang, may be the keyboard and mouse will not work so there should not be any other option other than a hard booting.

Why 'Value' types does not support inheritance ??

Why 'Value' types does not support inheritance ??

Few days back one of my friend has asked me this question, that time I couldn't think of any good answer that moment. Later I did some research and found that C# compiler( VB complier will do the same ) compile a structure as a "SEALED" class , which is why we can not inherit any "Structure"( read Value type ), now it raise another question why does the compiler compile it as a "SEALED" class ? is it by design ? what are the problems would happen if the compiler compile it as a normal(non-sealed in this context) class ?

After studying article of Jeffrey Ritcher, Tanj Bennett and others and discussing with my friends like Pal b and Richard and compiling my own thought with that ... here is what came out ...

It is not a limitation of C# or VB compiler, it's a limitation of .NET CLR. Though all data types (Reference-types as well as Value-types) in .NET are derived from the ultimate base class “Object”, structure in .NET has one very important advantages over class. I think that is the one of main reasons to introduce the concept of structure in .NET. And that is “Structure is lighter-weight than class”. Light-weight structure gives you better performance than class if you use it appropriately. To keep this “light-weightiness” behaviour of structure, .NET CLR considers it as a sealed class (actually all value-types are sealed class) - no object identity, no overheads for vptr (method pointer which is required to call virtual methods).

You might ask, then, how does structure support overriding methods (ToString, Equals, etc) of base class “Object”. It allows because in this case vptr will be inside “Object” class, not in structure. So, what's your take buddy ?