What does the " Burstable RAM " mean?

Does it mean you can use that amount?

E.G


256 Ram
1024 Burstable Ram


So it means a site could use all of the 1024MB of Ram the whole time? Or would the hosting company lower the allowance after a minute or two?

The burst RAM is there for when you need that bit extra but as the node becomes busier you might find it harder to get the RAM so you can't use it all the time. If you do you might find the host asks you to upgrade your package

Just remember burst ram is NOT guaranteed.

Always get the ram you need and do not *depend* on burst ram, or you'll have a "bad" vps experience.

What's my vps ram?

http://www.imageupload.com/uploads/96142_load.jpg (http://www.imageupload.com)

Hi!
I can't view the image..however..finding burst is normally easy.

do:

cat proc/user_beancounters

It's the privvmpages settings..just /256 and that will be MB RAM burst.

Bryon

cat proc/user_beancounters
is not working
in privvmpages there are soft limit hard limit and pages
Current Use Soft Limit Hard Limit Units Description
privvmpages 57,504 262,144 278,528 4KB pages Memory allocation limit

Hi!
No problem, then.
Soft=262,144= 1024MB
Hard=278,528= 1088MB

Bryon

cat proc/user_beancounters
is not working
in privvmpages there are soft limit hard limit and pages
Current Use Soft Limit Hard Limit Units Description
privvmpages 57,504 262,144 278,528 4KB pages Memory allocation limit

try cat /proc/user_beancounters

cat proc/user_beancounters
is not working
in privvmpages there are soft limit hard limit and pages
Current Use Soft Limit Hard Limit Units Description
privvmpages 57,504 262,144 278,528 4KB pages Memory allocation limit

try cat /proc/user_beancounters

Version: 2.5
uid resource held maxheld barrier limit failcnt
1003: kmemsize 3351707 3356728 44223692 45508198 0
lockedpages 0 0 1024 1024 0
privvmpages 73205 73336 262144 278528 0
shmpages 859 859 86016 86016 0
dummy 0 0 0 0 0
numproc 53 54 960 960 0
physpages 54112 54191 0 2147483647 0
vmguarpages 0 0 135168 2147483647 0
oomguarpages 55050 55129 104448 2147483647 0
numtcpsock 28 29 1440 1440 0
numflock 6 8 752 824 0
numpty 1 1 64 64 0
numsiginfo 0 1 1024 1024 0
tcpsndbuf 13368 15596 6881280 10813440 0
tcprcvbuf 0 692 6881280 10813440 0
othersockbuf 24072 29884 4504320 8388608 0
dgramrcvbuf 0 0 1048576 1048576 0
numothersock 19 23 1440 1440 0
dcachesize 602700 611310 13639680 14499840 0
numfile 1437 1438 37248 37248 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 47 47 512 512 0

According to this what my vps plan?

Hi!
Ohh..that's easy!

135168=RAM=528MB
262144 278528 =Burst RAM= 1024/1088MB
44223692 45508198 = Kmem= ~42/43.9 MB

As I said before..openvz recommends 15-17% of RAM to the kernel..so..that's not terrible..I have seen worse...but not good. It could cause problems down the road.

Bryon

Just remember burst ram is NOT guaranteed.

Always get the ram you need and do not *depend* on burst ram, or you'll have a "bad" vps experience.


How much ram do you need? Are there any guidlines to go by? Not for this person's specific needs but in general.


Anyone can answer.

Hi!
No way to tell..no general guidelines. I can tell you if you plan on building something from source...and even installing something big (Java App server)
what you will need to install is very different from what you will need to run it on a day to day basis. There is no way to know until you do it. Just an example...Cpanel used to run fine...espically for a person who just wanted to learn Cpanel..on a 128MB RAM VPS. Now...just to install it..you'll need twice that.

Day to day..128MB is probably fine..but you can't have everything running at the same time.

Bryon