View Single Post
Old 05-15-2016, 02:49 PM   #207
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by NiLuJe View Post
@geekmaster: If you were using -9, it *might* be an OOM issue?
Good point. Putting a swap file on SD card might resolve Out-Of-Memory issues, but with SD access SO SLOW on the K1, it may be a lot better to just use a lower compression rate (smaller compression block sizes). I cannot do swap over nbd when the K1 has no USB networking (or wifi), eh? And corkscrewing nbd through the amazon Whispernet proxy would be unwise (for many reasons), besides certainly being slower and higher latency than the SD card.

Regarding the low video frame rate on my K1, I already pointed out how the SD card is PAINFULLY SLOW when mounted in the K1. I have not done speed tests, but it is HUGELY FASTER to remove the SD card and connect it directly to my computer to transfer files. I suspect that either the K1 is doing 1-bit serial access (SPI) to the SD card, or the mmc kernel driver has the same problems it did when I "fixed" it (made it MUCH faster, then lost my source code) a decade ago: http://uanr.com/mmc/

Beware that a bad power supply can kill your work drive and ALL your backup hard drives. I should have backed up to CD and/or DVD back then...

Another problem is that gmplay naively does simple blocking reads and writes (and ioctl calls), to keep the code short and to the point (i.e. a demo). I could do async calls with double buffering, so the slow SD access overlaps the slow eink updates (but there was no need to add such extra complexity until now, discounting the slowness on DX/DXG).

It all depends on how I want to invest my limited hobby time (unless somebody is willing to PAY me to do kindle development).

Last edited by geekmaster; 05-15-2016 at 03:39 PM.
geekmaster is offline   Reply With Quote