Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I wrote a monolithic designed program which is quite rough on the processors needs. And as I have a dual-core I figured that one CPU should therefore be always at 100%. But both my CPUs are on 100% all the time. Now I am guessing that my compiler somehow turned my monolithic application in a threaded one. What are the limits of those optimization feature and when is it still needed to explicit make something threaded?
I am using the gcc on Ubuntu linux 64-Bit
It doesn’t, at least not without using something like Cilk. You must be inadvertently using multiple threads (or processes) without realizing it. Perhaps you’re using a third-party library that creates an extra thread or two in your process?
[EDIT]
As per the comments, use a program like
top(1)to verify that is in fact your program’s process that is using both CPUs at 100%. In your case, the XORG process is jumping to 100% because your program is producing a large amount of output.