User forums > Help
Slow perfomance on linux (Ubuntu Dapper)
Michael:
--- Quote from: sque on April 13, 2006, 06:42:07 am ---
--- Quote from: cyberkoa on April 13, 2006, 06:23:13 am ---I was using Ubuntu Breezy 5.10 a few days ago with the latest SVN (at that time) , very smooth and very unlikely encounter bug (though sometime will hang the session, need to switch to console to end)
could it because Dapper is still not stable yet ?
--- End quote ---
I was using breezy too before a couple of days and I had the same prob. Maybe its an ubuntu related thing...
btw, I dont compile source of code::blocks, I use the .deb that you give for ubuntu distros.
--- End quote ---
Hello,
.deb package are compiled under ubuntu 5.10 with standard ubuntu packages. Anyway, it could be interesting to try building C::B from SVN sources on Dapper (which AFAIK is stable, but needs some polish :)) and see if C::B is still slow.
Personally, I have not remarked this issue. Well, my desktop is old (PIII 500 MHz), but C::B works (scrolling, rendering, etc.) similar to many other applications.
Best wishes,
Michael
thomas:
Recently, I observed that a perverse amount of update_ui events are being sent around and postulated that this might possibly be one of the reasons for poor performance on some systems.
My problem is that I cannot reproduce the 100% load problem, so it is kind of hard to find out :)
However, this still looks promising:
When moving the mouse anywhere inside the Code::Blocks window (editor, manager pane, menu bar), I get a CPU usage of about 25% (averaged over a 1-minute interval). Removing a couple of EVT_UPDATE_UI entries reduces the CPU load to 12% on the same machine.
Now, I would like those having the 100% CPU problem to assist in confirming (or not confirming) that this may be a reason for your poor performance:
Edit src/main.cpp, plugins/compilergcc/compilergcc.cpp, and plugins/debuggergdb/debuggergdb.cpp, removing all lines containing EVT_UPDATE_UI.
Recompile Code::Blocks and see if the CPU load is still that high.
Note that you cannot actually use this modified version for normal development, as it does not properly update quite a few things any more! The purpose is just to verify whether this is where your CPU time goes.
Michael:
--- Quote from: thomas on May 05, 2006, 12:07:36 pm ---Now, I would like those having the 100% CPU problem to assist in confirming (or not confirming) that this may be a reason for your poor performance:
Edit src/main.cpp, plugins/compilergcc/compilergcc.cpp, and plugins/debuggergdb/debuggergdb.cpp, removing all lines containing EVT_UPDATE_UI.
Recompile Code::Blocks and see if the CPU load is still that high.
--- End quote ---
Hello,
If you temporary commit the changes (alternatively, I can also apllied the change locally :)), I can build a .deb package and make it available on my File Hosting for those using Ubuntu.
Best wishes,
Michael
thomas:
Uh... I cannot possibly commit that :shock:
With these event table entries removed, none of the menus will be properly updated, the application will be utterly unusable. :P
It is really easy to do the modifications locally, though. Just search for EVT_UPDATE_UI in those 3 files, or do a global search.
The EVT_UPDATE_UIs are all grouped in one large bunch, so you only need to select 10-20 lines and press Ctrl-Shift-C every time :)
I did not upload a patch because it is so trivial really.
Michael:
--- Quote from: thomas on May 05, 2006, 01:11:54 pm ---Uh... I cannot possibly commit that :shock:
With these event table entries removed, none of the menus will be properly updated, the application will be utterly unusable. :P
--- End quote ---
Yes, you are right. It will make more problems than anything else.
--- Quote from: thomas on May 05, 2006, 01:11:54 pm ---It is really easy to do the modifications locally, though. Just search for EVT_UPDATE_UI in those 3 files, or do a global search.
The EVT_UPDATE_UIs are all grouped in one large bunch, so you only need to select 10-20 lines and press Ctrl-Shift-C every time :)
I did not upload a patch because it is so trivial really.
--- End quote ---
Ok, I will modifiy them now, build and upload in 2-3 hours (for the .deb package at least 90-120 minutes are necessary).
Best wishes,
Michael
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version