View Single Post
Posts: 167 | Thanked: 204 times | Joined on Jul 2010
#16
Originally Posted by vi_ View Post
If you want performance...

1. Do a complete reflash (unless you are convinced your setup is healthy)
2. Don't use widgetz
2. Install CSSU.
3. Install KP49.
4. Enable SR.
5. Change CPU speeds 500 low, 900 high.
6. Put swap on your SD card.
7. Apply some virtual memory tweaks.
8. Investigate compcache
9. Investigate swap reset script with cron/alarmd.
Thanks for this - am pleased to find that most of this is what I've been doing anyway. I've a few thoughts / questions on the latter points, though.

5. Running at 500/900 is fast, but, it's a fairly conservative improvement on the 500/805 that I was running before. Testing with 500/1100 feels really sleek - I really want this, and I accept full well that it's not optimal for battery life or (possibly) for device lifetime. I remain interested in achieving this on a transient, as-needed basis. In doing so, I'm also seeking to mitigate the impact on battery life by applying this on an as-needed basis, and should add some kind of safeguard against remaining in 1100MHz mode for too long in case of constant loading. What else am I not aware of?

6. Does the proposed benefit of this come from the assumption that the microSD card is fundamentally faster than the eMMC (not sure mine is), or from the fact that it is a separate device? I'm not filled with confidence by this thread either, is there a material benefit to this?

7. Good call, I've used Swappolube previously and neglected to reapply it after a reflash. Redone, with thanks for the reminder.

8. Thanks for the heads-up. Having read the entirety of this thread on compcache, I have gained the impression that reports are mixed and that we have a bunch of opinions - but no clear guidance or an obvious way to assess - how much use it will be to a given user in a given situation.
Am I correct in thinking that what makes the difference is not the overall amount of swap that is in use, but the amount of I/O to and from that swap that will (or won't) be made faster by caching to RAM?

If so, is there something sensible I can do with iostat or similar, to assess the size/frequency of reads/writes to/from the swap? I know broadly how to use it, but not necessarily how to use it to produce a test that anybody can run with comparable results, or how to interpret the results to determine whether it is likely to help.
9. How frequently do you find it worth refreshing the swap? I see a previous post from you that describes doing this nightly - is this still true? I currently perform a nightly cycle of reboot -> automated backupmenu -> reboot -> rsync to remote machine every day at 0430, provided that we're on charge, not in use and on the home WiFi network. So, since I rarely reach an uptime of 24 hours in the name of having good backups, I suspect this is redundant as far as I am concerned.

I'd be interested in your thoughts... and thanks for your input on this so far.