User forums > Help
Slow perfomance on linux (Ubuntu Dapper)
TheTuxKeeper:
--- Quote from: Game_Ender on June 17, 2006, 04:59:16 pm ---Taking those out seems to have no effect. I am using the autotools build which compiles with -g no matter what I do, so that might have some effect. I will compare the normal Code::Blocks performance on Linux both autotools and CB based builds, then I will check out the nightly on windows and report back.
--- End quote ---
I didn't test this, but you can try to remove the -g flag in the CXXFLAGS variable in config.status (only available after running ./configure), touch one Makefile.am and then run make again. It will update the Makefiles automatically with the variables values that are stored in config.status.
Edit: Now I checked it and it works. The -g disappeared ;)
--- Quote from: Game_Ender on June 17, 2006, 04:59:16 pm ---Does anyone have a good Linux profiling tool that will handle shard libraries?
--- End quote ---
Don't know whether it helps you, but I found http://en.wikipedia.org/wiki/Performance_analysis . There you find few links to profilers. I just wanted to know what a profiler is and found it :lol:
Game_Ender:
Thank you for the autotools tip. Do you know if autoconf can be made to include architecture specific optimizations when configureing?
TheTuxKeeper:
--- Quote from: Game_Ender on June 17, 2006, 07:26:17 pm ---Thank you for the autotools tip. Do you know if autoconf can be made to include architecture specific optimizations when configureing?
--- End quote ---
I have only little experience with autotools (read few parts of this "Autotools Tutorial" eBook).
But take a look at acinclude.m4. There is a target and a platform check ( the CODEBLOCKS_GET_PLATFORM or the CODEBLOCKS_SETUP_FOR_TARGET part at the beginning). The architecture is the first part of the target string ( target = $CPU-$VENDOR-$OS ).
In line 188 of acinclude.m4 is also a platform check (for the xp-manifest plugin).
AFAICS it can be done with bash/sh ifs and cases ;)
Hope these hints can help you. :)
I can't give you a more exactly answer because I don't know these things, I'm learning them by reading the existing code (I didn't even know what I wrote above when I read your post :mrgreen:).
Game_Ender:
I haven't had a chance to use this, but I think found a good profiler to use with CB. Gprog/sprof are pretty hard to use because of all the shared libraries CB uses. Sysprof, which is a kernel module and application, let you profile the any application in the system. Hope this helps the CB team.
Jabber:
Hi,
I'm having the same problems on Debian Etch (=Testing). I tested the current SVN against self-compiled wxGTK 2.6.2 ANSI builds and wxGTK 2.6.3 Unicode builds; both show the awfully slow editor behaviour. Scite isn't blazing fast, but compared to C::B not slow at all.
Is there anything I can do to trace this down? I've got no experience with profiling and would need some detailed instructions...
Jabber
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version