Multithreaded Application by CreateThread() causes High CPU Usage
up vote
-3
down vote
favorite
I wrote multithreaded application running on windows 7, but while it's running, application is eating CPU time up so much.
Code is in C and just like below
first thread reads data from a file and second thread polls a graph from data read from file continuously
I tried "thread priority" but I got same result,
How can i solve this problem
DWORD WINAPI Thread1Function(LPVOID Param){
Initialising Parameters...
while(1){
}
}
DWORD WINAPI Thread2Function(LPVOID Param){
Initialising Parameters...
while(1){
}
}
main(){
Thread1=CreateThread(NULL,0,Thread1Function,NULL,0,Thread1_ID);
Thread2=CreateThread(NULL,0,Thread2Function,NULL,0,Thread2_ID);
while(1){
}
}
Thank you
c multithreading winapi
add a comment |
up vote
-3
down vote
favorite
I wrote multithreaded application running on windows 7, but while it's running, application is eating CPU time up so much.
Code is in C and just like below
first thread reads data from a file and second thread polls a graph from data read from file continuously
I tried "thread priority" but I got same result,
How can i solve this problem
DWORD WINAPI Thread1Function(LPVOID Param){
Initialising Parameters...
while(1){
}
}
DWORD WINAPI Thread2Function(LPVOID Param){
Initialising Parameters...
while(1){
}
}
main(){
Thread1=CreateThread(NULL,0,Thread1Function,NULL,0,Thread1_ID);
Thread2=CreateThread(NULL,0,Thread2Function,NULL,0,Thread2_ID);
while(1){
}
}
Thank you
c multithreading winapi
1
In the example shown, your 3 threads (main and 2 workers) are all running tight unyielding loops, that is what eats up all the CPU cycles. Make sure your worker threads are performing yielding operations periodically (in your example, you can useSleep()
for testing), and change your main thread to useWaitForMultipleObjects()
instead of a loop to wait on worker threads, and you will see CPU usage go way down.
– Remy Lebeau
Nov 19 at 21:56
What problem are you trying to solve? Continuously doing work without expending system resources?
– IInspectable
Nov 19 at 22:01
Using more of the resources of the processor (== driving the cpu usage up) is one primary reason to use threads.
– Hans Passant
Nov 19 at 23:18
You have literally designed an app to keep 3 CPU cores hot. If this is not your goal then (a) use less threads and/or (b) Use message queues or wait objects to block until theres work to do.
– Chris Becke
Nov 20 at 7:32
IInspectable, trying to solve high CPU usage, I have never faced problem with "continuously doing work" because I have already used endless loop. Problem is when I use endless loop either in thread functions or main function, windows take almost all CPU time to run the application. I try to reduce CPU time that application uses
– Baris Erdogan
Nov 20 at 18:19
add a comment |
up vote
-3
down vote
favorite
up vote
-3
down vote
favorite
I wrote multithreaded application running on windows 7, but while it's running, application is eating CPU time up so much.
Code is in C and just like below
first thread reads data from a file and second thread polls a graph from data read from file continuously
I tried "thread priority" but I got same result,
How can i solve this problem
DWORD WINAPI Thread1Function(LPVOID Param){
Initialising Parameters...
while(1){
}
}
DWORD WINAPI Thread2Function(LPVOID Param){
Initialising Parameters...
while(1){
}
}
main(){
Thread1=CreateThread(NULL,0,Thread1Function,NULL,0,Thread1_ID);
Thread2=CreateThread(NULL,0,Thread2Function,NULL,0,Thread2_ID);
while(1){
}
}
Thank you
c multithreading winapi
I wrote multithreaded application running on windows 7, but while it's running, application is eating CPU time up so much.
Code is in C and just like below
first thread reads data from a file and second thread polls a graph from data read from file continuously
I tried "thread priority" but I got same result,
How can i solve this problem
DWORD WINAPI Thread1Function(LPVOID Param){
Initialising Parameters...
while(1){
}
}
DWORD WINAPI Thread2Function(LPVOID Param){
Initialising Parameters...
while(1){
}
}
main(){
Thread1=CreateThread(NULL,0,Thread1Function,NULL,0,Thread1_ID);
Thread2=CreateThread(NULL,0,Thread2Function,NULL,0,Thread2_ID);
while(1){
}
}
Thank you
c multithreading winapi
c multithreading winapi
edited Nov 19 at 19:58
OznOg
2,32411525
2,32411525
asked Nov 19 at 19:13
Baris Erdogan
1
1
1
In the example shown, your 3 threads (main and 2 workers) are all running tight unyielding loops, that is what eats up all the CPU cycles. Make sure your worker threads are performing yielding operations periodically (in your example, you can useSleep()
for testing), and change your main thread to useWaitForMultipleObjects()
instead of a loop to wait on worker threads, and you will see CPU usage go way down.
– Remy Lebeau
Nov 19 at 21:56
What problem are you trying to solve? Continuously doing work without expending system resources?
– IInspectable
Nov 19 at 22:01
Using more of the resources of the processor (== driving the cpu usage up) is one primary reason to use threads.
– Hans Passant
Nov 19 at 23:18
You have literally designed an app to keep 3 CPU cores hot. If this is not your goal then (a) use less threads and/or (b) Use message queues or wait objects to block until theres work to do.
– Chris Becke
Nov 20 at 7:32
IInspectable, trying to solve high CPU usage, I have never faced problem with "continuously doing work" because I have already used endless loop. Problem is when I use endless loop either in thread functions or main function, windows take almost all CPU time to run the application. I try to reduce CPU time that application uses
– Baris Erdogan
Nov 20 at 18:19
add a comment |
1
In the example shown, your 3 threads (main and 2 workers) are all running tight unyielding loops, that is what eats up all the CPU cycles. Make sure your worker threads are performing yielding operations periodically (in your example, you can useSleep()
for testing), and change your main thread to useWaitForMultipleObjects()
instead of a loop to wait on worker threads, and you will see CPU usage go way down.
– Remy Lebeau
Nov 19 at 21:56
What problem are you trying to solve? Continuously doing work without expending system resources?
– IInspectable
Nov 19 at 22:01
Using more of the resources of the processor (== driving the cpu usage up) is one primary reason to use threads.
– Hans Passant
Nov 19 at 23:18
You have literally designed an app to keep 3 CPU cores hot. If this is not your goal then (a) use less threads and/or (b) Use message queues or wait objects to block until theres work to do.
– Chris Becke
Nov 20 at 7:32
IInspectable, trying to solve high CPU usage, I have never faced problem with "continuously doing work" because I have already used endless loop. Problem is when I use endless loop either in thread functions or main function, windows take almost all CPU time to run the application. I try to reduce CPU time that application uses
– Baris Erdogan
Nov 20 at 18:19
1
1
In the example shown, your 3 threads (main and 2 workers) are all running tight unyielding loops, that is what eats up all the CPU cycles. Make sure your worker threads are performing yielding operations periodically (in your example, you can use
Sleep()
for testing), and change your main thread to use WaitForMultipleObjects()
instead of a loop to wait on worker threads, and you will see CPU usage go way down.– Remy Lebeau
Nov 19 at 21:56
In the example shown, your 3 threads (main and 2 workers) are all running tight unyielding loops, that is what eats up all the CPU cycles. Make sure your worker threads are performing yielding operations periodically (in your example, you can use
Sleep()
for testing), and change your main thread to use WaitForMultipleObjects()
instead of a loop to wait on worker threads, and you will see CPU usage go way down.– Remy Lebeau
Nov 19 at 21:56
What problem are you trying to solve? Continuously doing work without expending system resources?
– IInspectable
Nov 19 at 22:01
What problem are you trying to solve? Continuously doing work without expending system resources?
– IInspectable
Nov 19 at 22:01
Using more of the resources of the processor (== driving the cpu usage up) is one primary reason to use threads.
– Hans Passant
Nov 19 at 23:18
Using more of the resources of the processor (== driving the cpu usage up) is one primary reason to use threads.
– Hans Passant
Nov 19 at 23:18
You have literally designed an app to keep 3 CPU cores hot. If this is not your goal then (a) use less threads and/or (b) Use message queues or wait objects to block until theres work to do.
– Chris Becke
Nov 20 at 7:32
You have literally designed an app to keep 3 CPU cores hot. If this is not your goal then (a) use less threads and/or (b) Use message queues or wait objects to block until theres work to do.
– Chris Becke
Nov 20 at 7:32
IInspectable, trying to solve high CPU usage, I have never faced problem with "continuously doing work" because I have already used endless loop. Problem is when I use endless loop either in thread functions or main function, windows take almost all CPU time to run the application. I try to reduce CPU time that application uses
– Baris Erdogan
Nov 20 at 18:19
IInspectable, trying to solve high CPU usage, I have never faced problem with "continuously doing work" because I have already used endless loop. Problem is when I use endless loop either in thread functions or main function, windows take almost all CPU time to run the application. I try to reduce CPU time that application uses
– Baris Erdogan
Nov 20 at 18:19
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53381174%2fmultithreaded-application-by-createthread-causes-high-cpu-usage%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
In the example shown, your 3 threads (main and 2 workers) are all running tight unyielding loops, that is what eats up all the CPU cycles. Make sure your worker threads are performing yielding operations periodically (in your example, you can use
Sleep()
for testing), and change your main thread to useWaitForMultipleObjects()
instead of a loop to wait on worker threads, and you will see CPU usage go way down.– Remy Lebeau
Nov 19 at 21:56
What problem are you trying to solve? Continuously doing work without expending system resources?
– IInspectable
Nov 19 at 22:01
Using more of the resources of the processor (== driving the cpu usage up) is one primary reason to use threads.
– Hans Passant
Nov 19 at 23:18
You have literally designed an app to keep 3 CPU cores hot. If this is not your goal then (a) use less threads and/or (b) Use message queues or wait objects to block until theres work to do.
– Chris Becke
Nov 20 at 7:32
IInspectable, trying to solve high CPU usage, I have never faced problem with "continuously doing work" because I have already used endless loop. Problem is when I use endless loop either in thread functions or main function, windows take almost all CPU time to run the application. I try to reduce CPU time that application uses
– Baris Erdogan
Nov 20 at 18:19