Threading Priority?
-
I’m creating a network application which consists of a server and client-both windows applications, for each client that connects to the server the server will create a thread to handle that clients requests. One of the features will need to have very accurate and fast transfers between the client and server, which means that the server will need to run very efficiently, since I don’t want to restrict the server to run on dedicated hardware I was thinking of making the priority higher, which brings me to my question: Should I set each thread that handles a client to a higher priority, or should I set the process from the server application to a higher priority. And will I achieve better performance if I set both to a higher priority or setting one to high is the same as setting both (in other words, does windows have 5 levels of priority or 25 (5x5) levels of priority? ) Answers to any part of this post will be greatly appreciated.
-
I’m creating a network application which consists of a server and client-both windows applications, for each client that connects to the server the server will create a thread to handle that clients requests. One of the features will need to have very accurate and fast transfers between the client and server, which means that the server will need to run very efficiently, since I don’t want to restrict the server to run on dedicated hardware I was thinking of making the priority higher, which brings me to my question: Should I set each thread that handles a client to a higher priority, or should I set the process from the server application to a higher priority. And will I achieve better performance if I set both to a higher priority or setting one to high is the same as setting both (in other words, does windows have 5 levels of priority or 25 (5x5) levels of priority? ) Answers to any part of this post will be greatly appreciated.
I think it would depend on what else is going happening on the server. if you don't have a lot of activity i would leave the priority where it is. i built an application that handles threads like you have for developers to "bounce" IIS when there is a vb6 dll that has to be replaced. I also through in IM and Chat for some extra features. I have never noticed any slowness no matter how much activity my server piece is getting and each response is close to immediate.