Author Topic: Code::Blocks slow as molasses  (Read 25288 times)

SirMike

  • Guest
Re: Code::Blocks slow as molasses
« Reply #30 on: April 29, 2006, 01:50:50 pm »
I can also add that tested those apps with disabling any possible options related to editor.

takeshimiya

  • Guest
Re: Code::Blocks slow as molasses
« Reply #31 on: April 29, 2006, 02:13:52 pm »
SirMike: could you try to profile Code::Blocks?

SirMike

  • Guest
Re: Code::Blocks slow as molasses
« Reply #32 on: April 29, 2006, 02:43:37 pm »
SirMike: could you try to profile Code::Blocks?

Sure - cannot do it right now but I'll try as soon as I'm back at home.

SirMike

  • Guest
Re: Code::Blocks slow as molasses
« Reply #33 on: April 29, 2006, 04:56:50 pm »
OK, I recompiled C::B with -pg and ran gprof.

I just fired C::B, wrote simple program (like Hello World with some functions) copied some text, scrolled several times.

You can find the result in an attached file.

[attachment deleted by admin]

Offline thomas

  • Administrator
  • Lives here!
  • *****
  • Posts: 3979
Re: Code::Blocks slow as molasses
« Reply #34 on: April 29, 2006, 05:24:18 pm »
For such profiling to be effectively usable, you have to disable all plugins and scroll for a long time (20-40 seconds). For profiling to be valid, the thing you want to measure must be isolated as much as can be done.

Otherwise, the CPU time that goes into startup (loading plugins, config, lexers) skews the measuring beyond any good use. Imagine what happens if the code parser runs over your source while you scroll. What will appear in the profile?
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

SirMike

  • Guest
Re: Code::Blocks slow as molasses
« Reply #35 on: April 29, 2006, 06:04:07 pm »
Weird, I did more scrolling and typing but results are almost the same this time :|

[attachment deleted by admin]

Sherwood

  • Guest
Re: Code::Blocks slow as molasses
« Reply #36 on: May 06, 2006, 02:34:08 am »
I have had the same speed problem with debian etch.
I don't think it's a Code::Blocks problem: The SAME .deb I used in debian etch works fine on Ubuntu 5.10 (which I just installed).

The problem must be in a new version of a Code::Blocks dependency (wx, provably).

We could isolate the problem, trying with increasing versions of the libraries used by Code::Blocks...
I know, that's a pain in the ass, but...

- SW

By the way, this one is the nicets IDE I know! Keep going!