User forums > Using Code::Blocks

C::B : a CPU consumer ?

<< < (2/5) > >>

Commodore64:

--- Quote from: DonSixto on October 26, 2006, 03:24:56 am ---I'm sorry to tell you that you are out of place.
This post offends me.

--- End quote ---
I don't agree at all with you.

First, I don't see why a program should employ more CPU time than what it needs. I'm not saying that C::B takes too much CPU time; but, as a general rule, less is better ;)

One reason why a lower CPU usage is desirable is power. This summer I have been programming with C::B in a nice mountain place, under the wood with my laptop... well, I wanted to maximize my battery's life, and I wasn't too happy that, almost every time I scrolled code, the frequency and voltage of my CPU were increased by the CPU driver, and the CPU fan turned on...

And I don't like general statements like "if you are using a Windows 2003 as a data and application server, you are doing wrong". Who says that? And why cannot I use, for example, a Windows 2003 machine as a terminal server with many programmers logged in, doing their job with C::B? Why should I always buy underutilized new hardware if old hardware can do the job well?

Rockeye:

--- Quote from: DonSixto on October 26, 2006, 03:24:56 am ---I'm sorry to tell you that you are out of place.
This post offends me.

--- End quote ---

 :shock: :shock: :shock:
You are shocked because an idle IDE consumes CPU time ???

I was just curious, and wonder if it is a well known issue or a bug in my laptop.

As Commordore64, I am working on a laptop and I pay a great attention to the CPU consumption. I expect an idle appplication such as notepad to not use ANY CPU time. And C::B is an extended Notepad when idle (sorry for developpers, don't be offended, you do a great IDE  :D).

C::B uses cpu even when all parsing processes and others are terminated, neither compilation, nor debug running. So I wonder : "Why ?"

Is it an isolated case or other users are concerned ?

>Ceniza : The mouse is not involved in my case because when C::B is minimized with a project open and several files (7) opened in the editor, it consumes at least 10%...

tiwag:

--- Quote from: Rockeye on October 26, 2006, 10:53:34 am ---C::B uses cpu even when all parsing processes and others are terminated, neither compilation, nor debug running. So I wonder : "Why ?"

--- End quote ---
make a cpu load diagram using process-explorer or any similar tool,

when i do this, i can see that CB doesn't have any cpu load (after the initial file loading, code parsing, etc...) when CB is minimized  :?




brgds

DonSixto:

--- Quote from: Commodore64 on October 26, 2006, 10:18:49 am ---I don't agree at all with you.

--- End quote ---
I am sorry if I bothered.



--- Quote from: Commodore64 on October 26, 2006, 10:18:49 am ---First, I don't see why a program should employ more CPU time than what it needs. I'm not saying that C::B takes too much CPU time; but, as a general rule, less is better ;)

--- End quote ---
Yep, you are right.
I think it's just a matter of time, and developers will improve C::B the way you want.
But in the meantime, how about making a donation ?
It would encourage them to do so.
I am happy with current version.
I will have to donate.


--- Quote from: Commodore64 on October 26, 2006, 10:18:49 am ---And I don't like general statements like "if you are using a Windows 2003 as a data and application server, you are doing wrong". Who says that? And why cannot I use, for example, a Windows 2003 machine as a terminal server with many programmers logged in, doing their job with C::B? Why should I always buy underutilized new hardware if old hardware can do the job well?

--- End quote ---
I say so.
You misunderstood me in this point.
I found that when you have a data server deamon that uses tcp/ip in win srv 2003, when it is serving several requests and generates more than a million packets in a matter of minutes, if you compile something in the same computer somehow the windows loses packets, causing undesirable results.
And I found too that an old computer, say a pentium iii 500 mhz with 256MB, performs very well for c++ development with C::B and other IDEs too.
But what I definitely can't do is data serving and compilations in the same windows computer. The other employees complain because they notice the server too slow. And they are right to complain. They have the customers in front of them and the attention should be quick and of the best quality.

Once more, I'm sorry if I bothered.
Sometimes, something may be offensive to me if it is written in certain way.
And more when it's about a very good open source tool that I'm happy to be able to use.
My apologies to you all.

Kind regards.


Commodore64:

--- Quote from: DonSixto on October 26, 2006, 03:21:21 pm ---I think it's just a matter of time, and developers will improve C::B the way you want.

--- End quote ---

Yep, nothing is perfect in this world   :)
But if we all are using Code::Blocks, it is because we find it "more" perfect than the competition  8)


--- Quote from: DonSixto on October 26, 2006, 03:21:21 pm ---I found that when you have a data server deamon that uses tcp/ip in win srv 2003, when it is serving several requests and generates more than a million packets in a matter of minutes, if you compile something in the same computer somehow the windows loses packets, causing undesirable results.
And I found too that an old computer, say a pentium iii 500 mhz with 256MB, performs very well for c++ development with C::B and other IDEs too.
But what I definitely can't do is data serving and compilations in the same windows computer. The other employees complain because they notice the server too slow. And they are right to complain. They have the customers in front of them and the attention should be quick and of the best quality.

--- End quote ---

You're right, Windows is all but perfect  :lol: even if one would expect something more, given its cost and its level of sophistication.
However, I think that anybody should be free to try and use the solution more suitable to its needs... I'm not an expert, but I think that an application server with Windows Server 2003 can manage a reasonable number of users programming concurrently (if it is not used as a data server... as you say!)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version