maemo.org - Talk - ANNOUNCE: Diablo-Turbo first beta available

Page 44 of 62

« First

< Prev

Next >

Last »

Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)

- OS2008 / Maemo 4 / Chinook - Diablo (https://talk.maemo.org/forumdisplay.php?f=29)

- - ANNOUNCE: Diablo-Turbo first beta available (https://talk.maemo.org/showthread.php?t=69740)

tso	2011-07-13 11:28

Re: ANNOUNCE: Diablo-Turbo first beta available

Anyone else noticing ramzswap taking a nosedive from time to time?

lma	2011-07-13 14:03

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by tso (Post 1050081)

Anyone else noticing ramzswap taking a nosedive from time to time?

Not here (current uptime 69 days), but my setup may be different:

/proc/version:

Linux version 2.6.21-omap1 (miguel@linux) (gcc version 3.4.4 (release) (CodeSourcery ARM 2005q3-2)) #23 PREEMPT Sun Jan 16 13:38:22 CET 2011

(I know I should upgrade at some point) I think my current modules were hand-built from the latest compcache + maacruz's patches, but I can't find the build dir in my scratchbox right now. In any case, they're:

Code:

-rw-r--r--    1 root     root        18720 Feb  1 17:37 ramzswap.ko

-rw-r--r--    1 root     root         6960 Feb  1 17:37 xvmalloc.ko

/proc/ramzswap:
DiskSize: 131072 kB
NumReads: 139966
NumWrites: 61123
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
NotifyFree: 15626
ZeroPages: 698
GoodCompress: 80 %
NoCompress: 4 %
PagesStored: 24130
PagesUsed: 7716
OrigDataSize: 96520 kB
ComprDataSize: 29204 kB
MemUsedTotal: 30864 kB

(insmod'ed with disksize_kb=131072 memlimit_kb=32768)

jwernerny

2011-07-13 18:41

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by tso (Post 1050081)

Anyone else noticing ramzswap taking a nosedive from time to time?

I have, and I have disabled it from starting up.

I noticed that when running two or more large apps (i.e. canola, navit), while ramzswap was running, would see my n810 "bog-down" (get real slow) for several seconds. When I disabled ramzswap ("swapoff /dev/ramzswap0"), removed the kernel module ("rmmod ramzswap") and went back to using a dedicated partition for my swap space, things would run much more smoothly and consistently, even if slightly slower.

- John

maacruz

2011-07-13 21:51

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by tso (Post 1050081)

Anyone else noticing ramzswap taking a nosedive from time to time?

What do you mean by "nosedive"?
Slowdown?

tso	2011-07-13 22:34

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 1050476)

What do you mean by "nosedive"?
Slowdown?

Sorry, either crash or otherwise shut down.

I have sadly never caught it in the act, because my best indicator is that ASUI stops showing the orange long press indicator on the memory use readout.

GeraldKo

2011-07-14 01:27

Re: ANNOUNCE: Diablo-Turbo first beta available

Well, I just installed (or think I did) the CSSU and Diablo-Turbo.

When I enter

Code:

uname -a

, however, I get:

Code:

Linux Nokia-N800-43-7 2.6.21-omap1 #2 PREEMPT Sun Mar 13 23:29:39 CET 2011 armv61 unknown

Was I supposed to actually get "noname" as part of the string (and not get "Nokia-N800-43-7"), or did I get to the new Diablo Turbo correctly?

The 43-7 in that string seems a bit surprising since "About Product" from the control panel says "Version: 5.2010.33-1". (5.2008.43-7 was the code for my pre-CSSU OS.)

The only oddity during installation was that I did not get an error about sysvinit on the main installation; I went ahead anyway and entered

Code:

dpkg -i sysvinit_2.85-22.osso15-dt1_armel.deb

, which did produce an error (which I ignored).

lidow

2011-07-14 05:16

Re: ANNOUNCE: Diablo-Turbo first beta available

Did you download all debs, including "Previous release" ones?

lma	2011-07-14 05:24

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by jwernerny (Post 1050338)

I noticed that when running two or more large apps (i.e. canola, navit), while ramzswap was running, would see my n810 "bog-down" (get real slow) for several seconds.

Sounds like you were using ramzswap only. That won't hold much data (especially with the default config) and so you can run out of virtual memory much earlier, causing the symptoms you describe. Canola and navit (is that stable these days btw?) probably store non-compressible data (images/sounds) which makes the situation worse.

IMO you really do need the swap file as well, just with a lower priority so that the compcache swap is used first while it has any space left.