I just deleted my PIE cache,,,, WOW 46 megs of cache. I did a few tests timing page downloads before deleting the cache, then timed the downloads again after deleting the cache. Some pages were faster before and some were faster after and only by a few seconds. So there was essentially zero difference in speed.
So what is the point of this massive 46 Meg allowance for PIE cache?
Related
I've been relatively happy with the performance of my Tilt, but I would like to see it a bit snappier on the portrait/landscape swap. I got KaiserTweak and the latest XML file and adjusted the File System Cache, File System Filter Cache, and GDI/Font Cache all to the "Advised" settings. However I didn't notice ANY increase in performance whatsoever. As a matter of fact, I think that the swap from landscape to portrait seemed even slower!
I tried setting all the caches to the highest setting and still nothing noticeable!
I know these settings have been around for some time (WM5) and I'm skeptical if they even really have any effect on WM6 phones. Maybe it does have some effect but it's just not noticeable to me.
Just curious...Does anyone noticeable an obvious performance bump by changing these settings???
Increasing the file system cache on the Kaiser wouldnt do any good. Since, we already have 128mb of RAM.
IMO having an increased page pool has a more impact than the system cache.
Follow this thread, it could shed a light to your question.
http://forum.xda-developers.com/showthread.php?t=335026
Not everything gets paged. Having a higher cache will help with some items. The filter cache shouldn't be set too high as this is not a size number, it's a file or sector number.
Use a 4mb or 4096 File cache size with 8192 sectors in the Filter cahce.
However, the cache will not help with screen rotation. That has absolutely nothing to do with cache size. Also, to as nebtioned above, changing you page pool to 16 or 18mb will give you a better performance increase than the cache settings will.
Setting a higher cache will only help speed thing up once they've been launched. Then they can be cached & future use will be sped up. Out of the box though, you won't see a lot of improvement
Hey guys,
I have some doubts in the cache in phone which need your expertise in.
Why is it that sometimes our phone will get sluggish and laggy, and we need to reboot it or clear cache to make it back to fast again? I thought in Android (linux), that ram is needed to run any applications and it does not depend on the space (data storage) we have left in the phone. So what does clearing cache has to do with the performance of the phone?
Thanks for your time.
Anyone have any ideas on this?
What are you talking about specifically? Clearing application cache? Doing this will have ZERO effect on device performance ***EXCEPT*** when running THAT SPECIFIC PROGRAM. It could make that program itself faster or slower to clear the cache. The purpose of cache is to improve performance by making the data available locally, however, if the data required is NOT IN CACHE, then having cache will slow it down as a result of having to process the cache.
Note: If you are running a custom hacked firmware using swap or compcache, then rebooting will clear some things up and make it faster. This is another form of cache that gets cleared. Ultimately, without frequent reboots, use of swap will tend to slow the device down over time, and this is cleared by rebooting.
Erm oki, so is it better to do without swap in this case as i'm using a custom firmware?
Let's say I am running 1 foreground application with 5 background applications (sleep) and another side running 1 foreground application with 15 background applications (sleep). This is just an example. In this 2 cases, will the speed of running the 1 foreground application be the same with the different number of background applications there?
Anyone have any ideas on this?
No one know anything about this issue?
I guess it's because the database gets huge and this may be bad for the performance...
so like a big registry in windows is bad...
maybe also some fragmentation... who knows
I thought I read about this before but I couldn't find it through Google. My browser went from 6mb to 10mb and now its 16mb of data but I haven't added any bookmarks and I clear the cache regularly. So wtf. Phone is stock, native browser
AndroidPerson said:
I thought I read about this before but I couldn't find it through Google. My browser went from 6mb to 10mb and now its 16mb of data but I haven't added any bookmarks and I clear the cache regularly. So wtf. Phone is stock, native browser
Click to expand...
Click to collapse
I haven't seen it get that big, but mine is always 6-10M when I look.. I really wish it limited itself and dumped the oldest data like any other browser cache does.
Restart your phone and the data will level out. Personally I had to reboot 3 times before it fixed itself. It's just one of those numerous Android quirks, they are relatively minor but annoying nonetheless
Search for the other thread on this, the browser was changed in froyo.
My phone seems to need to be reset about every 4 months or so because it completely runs out of storage space on the phone. The apps are on the sd card, clearing cache and dalvik cache only frees up a couple mbs. If I wipe it and start out with a fresh rom it starts out with something like 50 mb free. What's taking up all my disk space? Are there some files I can delete, like a temp folder or something?
Try to clean up some caches from applications like browser, feed reader, etc.
Settings -> Applications -> Manage Applications
Look at applications which might cache some internet data, i.e. browser, facebook, google+, maps, ... select them and clear cache. This should give you some more free space.
I wiped Dalvik/Art Cache from twrp being curious on my device. The boot took 30 seconds extra but that was okay. But now apps are delayed starting like white screen at first then starting with 1second delay!? Can anyone tell reason and a fix and the theory behind this?
You might know that Android runs apps in a "virtual machine", called Dalvik / ART. In computer science, a general principle to get things to run faster is to pre-compute them, or to re-organize them to make them run faster. It's exactly what's done with the Dalvik / ART cache - bits of program that are used and run more often are translated and organized into a language that your device can run faster and does not have to "re-interpret" each time the app is launched. This process takes some extra time and storage space, so that's why not all apps are necessarily optimized this way, but it's rather the Android OS that identifies recurrent code paths and tries its best to optimize them, based on complex heuristics.
The reason for which people sometimes suggest cleaning this cache is that you always want to make sure that the "optimized" code matches the actual apps and services you're running. If the optimized code doesn't match anymore, you might end up with some severe inconsistencies or some unpredictable bugs.
Over time, as you use your apps, their performance should get optimized again, based on your usage patterns, as the Dalvik / ART cache slowly gets filled up again.