Quote:
Originally Posted by kdusr
thanks Knc1, follow your hint, I found this command: mntroot rw , removed all images at screensaver folder 
then, I did a test,
step 1 : only copy one image bg_ss00.png to /usr/share/blanket/screensaver/ folder , this bg_ss00.png size is 2mb,
click power button to load screensaver
step 2 : copy another image bg_ss00.png to /usr/share/blanket/screensaver/ folder, overwrite old one, this time bg_ss00.png size is 100kb, click power button to load screensaver
measued time consum of those 2 diff images loading progress, The latter is at least twice as fast as the former，
what is this mean, as I understand, cpu need read and process those images data to ram, smaller image is faster because less data need to be processe, less data less ram  |
No.
It processes the data to the frame buffer.
And that is not how a Kindle's frame buffer based display works.
The entire frame buffer memory allocation is made when the kernel starts up and never changes.
It is a fixed allocation, its size never changes because it is allocated per pixel and the number of pixels on the screen is a fixed number.
Take a look at the various run time memory stats in /proc while you test things, see what changes and what does not.
= = = =
Also, you should do as you have been advised by myself and others above!
If the job you are trying to run is being killed for using too much memory, then do what Amazon does when it runs jobs that require a lot of ram - kill the processes owned by the user named: 'framework'
If you can't do that for some reason, then do what some of our developers do when they want to run a large job (such as a long running firmware compile) -
Enable swap.
There are plenty of directions posted here on doing that.
IIRC, there is even a KUAL menu extension for using swap.