View Single Post
Posts: 2,292 | Thanked: 4,135 times | Joined on Apr 2010 @ UK
#289
Originally Posted by peterleinchen View Post
swapped/flopped/moved is always (only) the currently used amount of swap memory (so maybe just 150MB or 200 or in my case max 450). But never more. So if I reduce the refresh actions I reduce the amount of write cycles on flash, right? [so your example with 200/day vs 700/3days do not match, afaiu]
The point I was making is it would be down to a lot of variables. If the system has most of it's RAM used and a large swap space it could be moving large amounts of swap as per my example.
It would depend on your swappiness and load at the time of swapping.
If you think about it you are writing to swap a lot with your usage anyway is switching swap only a "pee in the ocean" compared?
Then again I have never done any back to back testing. I'd find having any more than 2x800Mb would be a waste of valuable card space. I have all of my data on the card and backed up with rsync to a desktop.

Originally Posted by peterleinchen View Post
Do not get me wrong, I like flopswap and want to help make it better from the beginning (I have no intention to release a third/fourth swap refresh tool )
Thank you. Your help so far as been much appreciated, especially regarding the int32 issue I had.
You could use flopswap in the way you do (swapping less often with larger swaps), other than the fact there is no daemon, it is similar in GUI form. It is flexible in that way.
__________________

Wiki Admin
sixwheeledbeast's wiki
Testing Squad Subscriber
- mcallerx - tenminutecore - FlopSwap - Qnotted - zzztop - Bander - Fight2048 -


Before posting or starting a thread please try this.
 

The Following User Says Thank You to sixwheeledbeast For This Useful Post: