User forums > Using Code::Blocks

Code::Blocks slow as molasses

<< < (7/8) > >>

SirMike:
I can also add that tested those apps with disabling any possible options related to editor.

takeshimiya:
SirMike: could you try to profile Code::Blocks?

SirMike:

--- Quote from: Takeshi Miya on April 29, 2006, 02:13:52 pm ---SirMike: could you try to profile Code::Blocks?

--- End quote ---

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

SirMike:
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]

thomas:
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?

Navigation

[0] Message Index

[#] Next page

[*] Previous page