I really hope this doesn't kill my iPad. Can you do this directly on the iPad without file, or just with the trial version?
Yeah. Safari locked up a few times, which was more than annoying, so I'll wait for a more efficient solution.You can do it via the iFile trial or with OpenSSH for free!
I applied this hack, and it seems to work alright. Sometimes the iPad locks up though, which gets irritating, and booting takes a while. I wish I could solve this issue.
I really hope this doesn't kill my iPad. Can you do this directly on the iPad without file, or just with the trial version?
Sorry for all the random posts, but I do extensive testing on this type of stuff.
Turns out OpenSSH is the root problem to lockups for me now. Everything else that uses a daemon (mobile substrate) is Working perfectly fine and zero lock ups with over 16 tabs!
Hmmm...quite strange. Having removed SBSETTINGS (even without openSSH ever installed), the iPad with the VM .plist file doesn't lock up - but once installed SBSettings while using VM .plist hack, it crashes!
It's been more than 3 days now - ZERO crashes - this is with me backgrounding a ton of apps and having all 9 tabs open in safari!
Install today's Sbsettings.. works for me now. Didn't on the previous versions! I'm getting ready to take a screenshot..
I noticed SBSettings and backgrounder are updated today (or yesterday) - i'm going to download and install SBSettings again to see if it makes a difference!
Did it?
Iwanted to wait more than 24hrs time to report back in and with sbsettings beta 3.0.12 there have been no lockups and this is with the VM .plist running!!
I'm happy with overall performance.
Told ya! Been about 32 hours running straight here with ZERO issues. I can't get any apps to force close due to lack of memory ever now. The only thing that happens is that the ipad gets very sluggish when like 10+ apps are open with 10+ tabs lol... but surprisingly still very useful in this state.
even if you wrote to each individual cell multiple times daily they will still last hundreds (if not thousands) of years. deja vu
Everything I have read has never given that time frame.....in fact much much shorter
Doing a quick search:How much shorter is much much shorter than thousands of years?
http://blogs.computerworld.com/solid_state_disk_life_and_performance_varies_wildlyCoulson dismisses mean time to failure as an accurate metric for determining drive longevity, and instead says good solid state drives should be able to perform 3,000 8KB writes per second for five years. "Good solid state disks have sufficient life spans for enterprise applications," he said.
implying less than "decades"e other benefit from no latency is the drive will not suffer performance losses due to defragmentation. However unlike Hard drives which can last for decades. SSD drives memory wears out. If you are planning on running a highly transactional DB server, SSD drives would be fast, though they woud eventually wear out.
One recent study done with Intel SSDs is showing some strong evidence that some of their SSDs, the X25-M in particular, might have a serious issue with endurance. It appears that after the drives have been subjected to a few months of operation, their performance begins to suffer significantly. It was found that after spending a significant amount of time in a production environment, the drive begins to get heavily fragmented, due in part to the drive's own self-protection mechanism, wear leveling. The end result was a drive that could perform at only a fraction of its original glory, being reduced to speeds vastly lower than even mechanical desktop hard drives.
Will it last me 3-5 years?
So I just deleted the file that I made the apple.virtual memory one. Is that ok? Does that get rid of it? I just checked And now I have swapfile0 thru 4. Is that normal? Even after I deleted the apple.virtual memory file ?
Deleting the .plist file does indeed turn off the VM feature.. however since you previously were using VM turned on, it will leave the VM folder there with the swap files. You can go ahead and delete the VM folder with the swap files to free up that space being used up since it's not longer being accessed to clean your system be rid-free of VM.