Quote:
Originally Posted by muzicman82
What pagepool is everyone using on the Sprint Touch Pro for best performance??
|
I'm testing the beta2 with a 24mb pagepool just for kicks since we could be getting a juicy 8 official release soon.
(from what I understand) Higher PP =
- Increased application performance (TF3D, web browsing, Garmin, etc.)
- Decreased Battery Life (not sure how significantly affected)
- Decreased free RAM
But, with the fine releases graciously provided lately, increasing PP may provide diminishing returns with all the same negatives.
Quick google search returned a good post from 2006 explaining PP, quoted below. Link:
http://forum.brighthand.com/showthread.php?t=230392
Quote:
Several weeks ago, xda-developers community learned about one important setting in all wm5 devices, called PagePool, that can significantly boost speed (at expense of free RAM - tradeoffs, tradeoffs...) of pretty much every WM5 device out there. PagePool is the amount of RAM given to running a code at any given time. So the advantage of having a bigger PP is felt when you run several heavy programs at once. Here is comment from Mike Calligaro (from WM team):
RAM is used by 2 things: Data and Code. Any code that can’t execute in place (XIP) in ROM needs to be loaded into RAM and executed from there.
The page pool puts a cap on how much ram is used for code. No data is ever loaded into the pool. If you have a 2M page pool and regularly have 4M of code in use, you’ll spend a lot of time loading pages into the pool and unloading other pages from the pool. On the other hand, if you regularly have 4M of code in use and you have an 8M page pool, then you’ll just have 4M of the pool filled and the other 4M sitting idle. In that case, making the page pool larger would have absolutely no beneficial effect. All it would do is remove RAM that otherwise might have been used for Data.
|
Hope this helps.