as plasma starts to shape up into more and more of a usable application, i start to deal with that nagging voice in the back of my head that says, "dude, how's the memory consumption? call tree profile? do you have any numbers?!" it's an annoying voice, mostly because i don't really have the time right now to do the work that would get her shut up. (yes, some of the voices in my head are female.)
if you would like to contribute to my personal sanity and help make plasma a better thing for everyone, you may wish to consider becoming plasma's official profiler. and by "official" i mean "someone who throws numbers and graphs at me". as you can see, my definition of official is pretty easy.
so what would this entail? gather up all the profiling tools you can find (this howto by seli is a great starting point for memory profiling and kcachegrind should be able to provide most of the rest), get a kde4 dev env up and running and start gathering numbers on plasma.
in my personal dream we'd have a historical set of data so we can see how resource consumption rises/falls over time. we'd also have a set of tasks we'd profile regularly. e.g. "start plasma, add the clock plasmoid, let it run for 5 minutes" might be one of those.
so if you are a "c" type personality who likes futzing around with your system and letting me know just how much my code sucks (and precisely where :) this just might be right up your alley.
as usual, you can find me on email or, slightly less frequently these days, irc.