Uh, pagepool?

[mdphoenix]

I'm searching and can't find the answer I'm looking for. So here goes.

First, what IS the pagepool. I've got the point that apparently increasing it's size makes for faster operation.

Second, what's an optimal size? Or does it depend on what we've cooked into our ROM?

Third, I've been using the PPCKitchen to cook my ROMs for the past week. Tweaking, and adjusting. Getting it just the way I want. There's an option to change the pagepool size. Can I do it with the kitchen? From what I've read, I get the impression that it won't work.

Fourth, can I brick my phone if I jack with the pagepool size?

As always, thanks much!

[hibby50]

optimal size depends on the phone. for the mogul it was 4 for the vogue it was 12 or 24 and for the pro it seems to be 36. the bigger it is the faster the rom but the less available ram u have and vice versa.

[pwrinxs]

I think Hibby means optimal is 32MB pagepool. Please correct me if I'm wrong.

[Compusmurf]

Mine is 32 and it's pretty decent. Not sure about the 36 tho.

[mdphoenix]

Ok. I'll go with 32. Now the question is how do I determine what mine currently is, and can I use the PPCKitchen to change it? Or will it not work?

[gguruusa]

Originally Posted by mdphoenix

Ok. I'll go with 32. Now the question is how do I determine what mine currently is, and can I use the PPCKitchen to change it? Or will it not work?

It works fine in PPCkitchen. What's broken is people trying to use the app PagePoolChanger.

Like Hibby said, it's a trade off. Experiment a bit, find what you like.

[mdphoenix]

Cool. Thanks again guys.

[chooch]

Does the 32MB come right out of the total (113MB I think on my vzw phone), and show up in the % of ram that is being used by windows? As in, if I cook with 12MB pagepool, I will see a lower percentage of ram being used by windows (at startup with no programs running) than if I cook with 32MB pagepool? If that's true, then I presume you wouldn't want to use a pagepool size that leaves you with like 99% of ram being used without opening any programs. . . that's what you mean by test it out right. . . finding the sweet spot for whatever you happen to have installed. Less resident stuff running would mean capability for bigger pagepool size, right? Hope that makes sense. Thanks for any input.

[gguruusa]

Originally Posted by chooch

Does the 32MB come right out of the total (113MB I think on my vzw phone), and show up in the % of ram that is being used by windows? As in, if I cook with 12MB pagepool, I will see a lower percentage of ram being used by windows (at startup with no programs running) than if I cook with 32MB pagepool? If that's true, then I presume you wouldn't want to use a pagepool size that leaves you with like 99% of ram being used without opening any programs. . . that's what you mean by test it out right. . . finding the sweet spot for whatever you happen to have installed. Less resident stuff running would mean capability for bigger pagepool size, right? Hope that makes sense. Thanks for any input.

I don't think it shows in the %, as it is part of the overhead layer. The rest of what you surmise is correct. Not just less resident stuff, but smaller stuff means opportunity for larger pagepool. On the flip side, allocating more than you need is pointless.

[mdphoenix]

Originally Posted by gguruusa

I don't think it shows in the %, as it is part of the overhead layer. The rest of what you surmise is correct. Not just less resident stuff, but smaller stuff means opportunity for larger pagepool. On the flip side, allocating more than you need is pointless.

Interesting point. What determines what you "need" as far as size of the pagepool?