I also have noticed the low efficience and I think it's very necessary to improve that. With a quick google search I've found a code profiler called gprof. It seems easy to use, it would require to compile gimp with an extra "-pg" and disable any compiler optimization.
I'm actually very novice yet and my knowledge on GIMP internals is pretty limited. So, those more expert developers: What do you think ? Would it be difficult to compile GIMP with gprof ? Would it be really useful for improving GIMP performance ?
Greetings
Guiu Rocafort
On Wed, Jul 18, 2012 at 3:45 PM, Aaron Paden <aaronbpaden@xxxxxxxxx> wrote:
So I mostly use MyPaint, but I'd like to be able to do some things in gimp, too. But gimp is way too slow on this computer. Especially trying to open large images like MyPaint encourages, I'll have to run to another tty to try and kill the process so I can continue to use my computer. I've got an old Pentium 4 with only about half a gig of RAM. A bit behind the times, but especially on Linux it's generally fast enough to get the job done.
Is there anything I can do to help improve performance? I don't have much experience. I doubt I could write anything any faster. But maybe I can do something to help identify bottlenecks? Anything I can do to help, I'm game.
_______________________________________________
gimp-developer-list mailing list
gimp-developer-list@xxxxxxxxx
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
_______________________________________________ gimp-developer-list mailing list gimp-developer-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gimp-developer-list
