User forums > Help

Serious performance issues on Ubuntu 6.10

(1/4) > >>

hendrik:
Hi all,

I already used Code::Blocks under Win32 for development in a larger project. CB is great work, so I decided to use it as the primary IDE for my next larger, platform-independent project, just to have a consistent development environment on win32, Linux and probably FreeBSD. After installation of a recent SVN version on Ubuntu 6.10, I realised that the editor component is really slow (it takes about half a second from my keyboard input until something appears on the screen), most input seems to lag behind, making text editing and usage of cut and paste a real pain (This is even trough for a minimal project containing only a single source file). This doesn't seem to be a problem of wxwidgets or the scintilla component, since both are used by Stanis Python Editor too, which runs perfectly on my Linux Box. Does anyone has some hints on how to increase performance of the CB editor?

stahta01:
Have you turned off the code completion plugin?

My guess a plugin is having an issue and turning them all off to see if issue goes away.
Then turn them on one at a time to see which one is the cause.

Tim S

rjmyst3:
I use C::B on Ubuntu 6.10, but I don't have the issues that you are describing . . .

EDIT: Using cstudent's november 17 nightly build for edgy

artoj:
I have the same problem, C::B uses about 30-40% of the CPU when typing. It's even worse when moving the mouse of the the toolbars, CPU usage raises over 50% (!). Scite uses about half of a amount CPU what C::B does, about 15-20% which is still way too much (the machine is a laptop). gedit uses about 5%.

The specs are:
Intel Pentium M 1,73GHz
1 GB RAM
Integrated graphics card (Intel)

Ubuntu 6.10, wxWidgets 2.6.3p2

And these results from C::B are with _no_ syntax highlighting; using one will raise the CPU usage even further.

EDIT: Forgot to add that I have only very small number of plugins enabled and among the disabled ones is code completion.

Game_Ender:
I have the same issues, but I believe autotools and the CB Project file only make unoptimized debug builds.  You should try an optimized build.  If you do a search you will see we have investigated this before.  The best I got was using sysprof to pin most of the work down to the editor component and Pango.  I suggest you install sysprof and give it a try.

Navigation

[0] Message Index

[#] Next page