maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)
-   -   Improving responsiveness under high memory load (https://talk.maemo.org/showthread.php?t=68125)

F2thaK 2011-03-30 04:48

Re: Improving responsiveness under high memory load
 
how to untar in xterm? thx

Bratag 2011-03-30 04:58

Re: Improving responsiveness under high memory load
 
Quote:

Originally Posted by f2thak (Post 978179)
how to untar in xterm? thx

tar xvf <file> for non gzipped
tar xvzf <file> for gzipped

F2thaK 2011-03-30 07:04

Re: Improving responsiveness under high memory load
 
just did this, bout to reboot.

will test tonight by downloading a big file thru transmission

thanks

F2thaK 2011-03-30 14:22

Re: Improving responsiveness under high memory load
 
i thought this app would help a cpu/ram hogging app work better..

it has made no difference to transmission for me anyway.

the app is still unresponsive and locks up phone

hawaii 2011-03-30 15:09

Re: Improving responsiveness under high memory load
 
Your ignorance is showing.

jprobichaud 2011-03-31 00:08

Re: Improving responsiveness under high memory load
 
Quote:

Originally Posted by Cirne (Post 916773)
Short answer: no, it won't work.

Long answer: I tried that at first (actually, a slightly more complex version of that; you can see the remnants of it in mlocker.c). The problem is that those processes aren't actually standalone binaries. The file you mention is just a symlink to maemo-invoker. maemo-invoker, in turn, talks to maemo-loader (a daemon), telling it "please run the rtcom-call-ui application". maemo-loader then opens up /usr/bin/rtcom-call-ui.launch and executes it. Only here's the rub, and why all the hassle with maemo-loader in the first place: the .launch files aren't actually executables. Oh, they're binaries, to be sure, but they're more like shared libraries with a main function. maemo-loader loads them and transfers control over to them without ever calling exec().

You can do an ls -l /proc/*/exe to see just how many processes are running with maemo-loader as their system-recognized primary executable. So, whatever hacks I'm going to do, they'll have to be more complex and target maemo-loader itself. I certainly plan to, at some point; might even throw a renice() in there too. It'd sure be keen if all the processes on the critical path didn't have to wait for page faults or processor scheduling when you get a phone call.


would it be possible to write a wrapper for the rt-comm-ui "shared library" and replace the wrapper script by a call to this wrapper instead of maemo-launcher? That would solve the shared lib issue and bring the phone app to be a "first class citizen".

Is that something doable or does maemo-launcher does extra magic that is hard to replicate?

F2thaK 2011-03-31 00:50

Re: Improving responsiveness under high memory load
 
Quote:

Originally Posted by hawaii (Post 978573)
Your ignorance is showing.

what IS your problem with me?

forgive me Im not an uber-geek like yourself, which is a good thing as I actually get laid.

pigeond 2012-01-09 22:05

Re: Improving responsiveness under high memory load
 
Hi there.

Perhaps I'm a bit late in joining in this. I was looking at using the mlock calls do similar things, and found this thread.

Any updates or new findings on the maemo-launcher business?

Basically I want to have some process not to be swapped out on the N900.

Thanks!


All times are GMT. The time now is 23:40.

vBulletin® Version 3.8.8