[Sugar-devel] Killing activities when memory gets short

Marco Pesenti Gritti marco at marcopg.org
Sun Aug 8 16:35:11 EDT 2010


On 8 Aug 2010, at 20:57, Lucian Branescu <lucian.branescu at gmail.com> wrote:
>>> 
>>> Separating the activity from the service would help here. In the case
>>> of music, MPD would use a lot less memory than one of its GUIs.
>> 
>> Right, I was thinking to something along these lines too. I'm not sure how the shell would enforce this policy though. Maybe we could allow the activity processes to use a minimum amount of memory when it has been asked to close. As I said, it gets complicated :)
> 
> An activity frontend to MPD could be killed following activity policy
> and the MPD daemon itself would be killed following regular daemon
> policy. Music would play after the activity dies and would only be
> stopped if the MPD daemon is killed (which is less likely since it
> uses very little memory).

Ah yeah that could work for global services. It would be good if the same could be done at activity level though. You could use the a similar mechanism but it would require figuring out how to launch these services, register them with the shell etc.

Marco


More information about the Sugar-devel mailing list