[Q] Any lag-fixes focusing on Cache and dbdata partitions, or low ram lag?

---

The current lag-fixes optimize application load times by changing the filesystem for "/data", and with that fix the phone does become a lot more responsive.

With /data optimized, I still notice a pretty bad lag when opening anything database related or cache related, for example: Adding a shortcut to the homescreen takes a good 15 seconds to load the list, I tried the same thing in a Droid X and it's instant... LauncherPro stalls everytime you do something for the first time, and then works ok, it loads animations to the cache so... (write times to cache maybe?)
Any thoughts on this? I haven't done all the research, so these are just my observations. (I've seen this with OneClick lagfix ext2, chainfire's 1.80 ext2 and ext4, and Tayutama's ext2 and ext4, on JM5, 6 and 7).

Another problem I have seen is the low ram lag, as soon as the phone dips under ~70MB of ram it becomes extremely sluggish, I haven't used a single firmware where I don't need autokiller with aggressive settings, again comparing to a nexus one or droid x, those phones work flawlessly with ~30MB free...

I haven't tried the Vooodoo lag fix, does that or any other lag-fix address this issues?

When I was running mimocan, I also moved/symlinked /dalvik-cache and /media to the external ext4 partition. Don't know how much it improved things, though.

Seems like running autokiller really is enough to address the memory management issue, maybe we'll see those settings tweaked in future firmwares.

Originally Posted by aeo087

The current lag-fixes optimize application load times by changing the filesystem for "/data", and with that fix the phone does become a lot more responsive.

With /data optimized, I still notice a pretty bad lag when opening anything database related or cache related, for example: Adding a shortcut to the homescreen takes a good 15 seconds to load the list, I tried the same thing in a Droid X and it's instant... LauncherPro stalls everytime you do something for the first time, and then works ok, it loads animations to the cache so... (write times to cache maybe?)
Any thoughts on this? I haven't done all the research, so these are just my observations. (I've seen this with OneClick lagfix ext2, chainfire's 1.80 ext2 and ext4, and Tayutama's ext2 and ext4, on JM5, 6 and 7).

Another problem I have seen is the low ram lag, as soon as the phone dips under ~70MB of ram it becomes extremely sluggish, I haven't used a single firmware where I don't need autokiller with aggressive settings, again comparing to a nexus one or droid x, those phones work flawlessly with ~30MB free...

I haven't tried the Vooodoo lag fix, does that or any other lag-fix address this issues?

Originally Posted by aeo087

The current lag-fixes optimize application load times by changing the filesystem for "/data", and with that fix the phone does become a lot more responsive.

With /data optimized, I still notice a pretty bad lag when opening anything database related or cache related, for example: Adding a shortcut to the homescreen takes a good 15 seconds to load the list, I tried the same thing in a Droid X and it's instant... LauncherPro stalls everytime you do something for the first time, and then works ok, it loads animations to the cache so... (write times to cache maybe?)
Any thoughts on this? I haven't done all the research, so these are just my observations. (I've seen this with OneClick lagfix ext2, chainfire's 1.80 ext2 and ext4, and Tayutama's ext2 and ext4, on JM5, 6 and 7).

Another problem I have seen is the low ram lag, as soon as the phone dips under ~70MB of ram it becomes extremely sluggish, I haven't used a single firmware where I don't need autokiller with aggressive settings, again comparing to a nexus one or droid x, those phones work flawlessly with ~30MB free...

I haven't tried the Vooodoo lag fix, does that or any other lag-fix address this issues?

Nope, Voodoo doesn't address it either. /dbdata acts strangely if you try to mess with it and seems to cause some strange issues, which is why it has been left out of fixes so far. Plus, /dbdata is on very fast NAND which doesn't suffer so much as the sdcard from RFS.

Low ram lag is probably touchwizz related, or if not touchwizz, than some other badly done Samsung modification. Unfortunately that kind of thing is very hard to find. It could be something completely unrelated though, like a badly made driver that behaves badly when RAM is low.

Originally Posted by RyanZA

Nope, Voodoo doesn't address it either. /dbdata acts strangely if you try to mess with it and seems to cause some strange issues, which is why it has been left out of fixes so far. Plus, /dbdata is on very fast NAND which doesn't suffer so much as the sdcard from RFS.

Low ram lag is probably touchwizz related, or if not touchwizz, than some other badly done Samsung modification. Unfortunately that kind of thing is very hard to find. It could be something completely unrelated though, like a badly made driver that behaves badly when RAM is low.

Am I right to say that that lag when adding a shortcut or accessing the list of apps comes from dbdata? why is the phone so slow at pulling up that information? Also, have you seen any performance benefit from optimizing the cache partition?