dcop services

John Ratke jratke at comcast.net
Fri Oct 10 13:08:13 BST 2003


George Staikos wrote:

>On Friday 10 October 2003 03:34, Tobias Koenig wrote:
>  
>
>>On Thu, Oct 09, 2003 at 10:30:48PM -0400, George Staikos wrote:
>>Hi George,
>>
>>    
>>
>>>Are DCOP services supposed to go away over time, and if so, when?  They
>>>seem to run forever here after all apps that are using them close.
>>>KWeatherservice, cvsservice, rssservice are particular examples.
>>>      
>>>
>>I use kweatherservice and rssservice in kontact and I don't kill them
>>explicitely, because I would have to start them next time kontact is
>>restartet and that would increase the start up time again...
>>I know it's a kind of wasting resources but I've no clue how to solve
>>this problem in a clean way.
>>    
>>
>
>  What's wrong with having them time out eventually?  I have to say that I 
>have 256 mb of ram right now and between debug build of kde running only kst, 
>konsole and kwhatsbroken, and huge leaks in my X server, I'm running into 
>swap.  Having KWeatherService running is quite painful and it makes a 
>difference when I kill it.  I imagine in must be much worse for those with 
>128mb.
>
>  
>
Right now, the weather panel applet does not call "exit" on the 
weatherservice.  This is probably because you could run the reportviewer 
or the weather bar in konq and both would require starting the service 
again.

I'm surprised that exiting the weatherservice makes that  much of a RAM 
difference.  Here are the numbers from my machine from top. 
21557 kde-deve   9   0  4968 3372 2392 S  0.0  1.3   0:11.18 kweatherservice
virtual: 4968
res: 3372
shared: 2392

I'm no memory expert, but isn't the amount of unique RAM for this 
process the res number minus the shared number?  If so, It's about a meg.

It would be nice if those numbers were lower.  I only have 256 mb 
myself, and I was thinking about taking a look and optimizing the RAM 
usage of kweatherservice, but I haven't had a chance yet.

In any event,  are you proposing that each service have a watchdog type 
timer that would time out and exit the service?  Or would the dcop 
system handle the timeout knowing that no services have been requested?  
What would the timeout be?  Half an hour?

-John






More information about the kde-core-devel mailing list