Results 1 to 7 of 7

Thread: VPS Beans...?

  1. #1
    Join Date
    Jan 2006
    Posts
    582

    * VPS Beans...?

    Hi

    Can anyone tell me if my beancounters look ok for a 512MB VPS


    resource held maxheld barrier limit failcnt
    kmemsize 6580636 6598333 48873472 73310208 0
    lockedpages 0 0 14744 16384 0
    privvmpages 109773 109780 471860 524288 0
    shmpages 9145 9145 524288 524288 0
    dummy 0 0 0 0 0
    numproc 107 107 500 500 307
    physpages 25679 25682 0 2147483647 0
    vmguarpages 0 0 131072 2147483647 0
    oomguarpages 29058 29061 131072 2147483647 0
    numtcpsock 26 26 500 500 1
    numflock 12 12 800 880 0
    numpty 1 1 255 255 0
    numsiginfo 31 31 2048 2048 0
    tcpsndbuf 4456 4456 21463040 41943040 0
    tcprcvbuf 0 692 21463040 41943040 0
    othersockbuf 22280 22280 6012928 16252928 0
    dgramrcvbuf 0 692 943720 1048576 0
    numothersock 35 35 500 500 0
    dcachesize 768586 771456 33554432 34537472 0
    numfile 1595 1596 52428 52428 0
    dummy 0 0 0 0 0
    dummy 0 0 0 0 0
    dummy 0 0 0 0 0
    numiptent 217 217 15360 15360 0


    Thanks in advance

    Keith

  2. #2
    Join Date
    Dec 2004
    Location
    Butler,TN
    Posts
    2,413
    Hi!
    No problem at all:

    Kmem=kernel memory= 48873472:73310208 = ~46MB-~70MB RAM = Good

    >>I've seen less than 10% of RAM given to the kernel (borderline) and as much as 20%. Yours fits safety in between those to..9-~14%. A little low...but as I said..I have seen much worse.

    RAM=512MB
    Burst=1843MB-2048MB RAM

    Looks good.

    Bryon
    Last edited by bryonhost1; 11-27-2006 at 05:43 PM.
    Bryon L Harvey
    Soil Relocation Engineer

  3. #3
    Join Date
    Jan 2006
    Posts
    582
    any major effect having it lower, would it run faster with more?

    Can this be set higher on request

    Cheers

    Keith

  4. #4
    Join Date
    Dec 2004
    Location
    Butler,TN
    Posts
    2,413
    Hi!
    Well..normally..what happens is you run out of resources..things don't work or compile correctly. A host may adjust the resource allocations temporarily for free..or may flat out insist you need to upgrade to the next level package.

    See that last column..failcnt? That keeps track of how many times whatever you have running on the VPS hits the allocation "wall". As you can see...you have only one parameter that has hit this wall..and it happened one time..numtcpsock.

    500 is about half what openvz recommends for a 512MB VPS...but it is up to each host to decide these parameters.

    Take a look:

    http://wiki.openvz.org/UBC_configuration_examples_table

    Each host differs..some will give you a little boost..some won't. Godaddy is the worst I've seen...6% kmem of RAM...sad...and they refuse to correct it.

    Bryon
    Bryon L Harvey
    Soil Relocation Engineer

  5. #5
    Code:
    2048 MB Allocation Limit [privvmpages limit]
    ****** only high value processes have a chance in this range
    ****** having this safety range is important to permit critical processes
    1843 MB Allocation Barrier [privvmpages barrier]
    ****** allocation requests in this range have a chance
     512 MB Allocation Guarantee [vmguarpages barrier]
    ****** allocation will succeed in this range
     512 MB Memory Guarantee [oomguarpages barrier]
     428 MB ( 428 MB Max) page memory allocated [privvmpages held]
     113 MB ( 113 MB Max) memory + swap used [oomguarpages held]
     100 MB ( 100 MB Max) page memory used [physpages held]
      69 MB ( 71592 KB) kernel memory limit [kmemsize limit]
    ****** a safety range here, between limit and barrier, is important
      46 MB ( 47728 KB) kernel memory barrier [kmemsize barrier]
       6 MB (  6426 KB) kernel memory used [kmemsize held]
       0 MB (    26 KB) buffer memory used [*buf held]
    -----------------------------------------------
     Used : Max_Used : Limit    for Other Resources
      1595    1596   52428   numfile
        12      12     880   numflock
       217     217   15360   numiptent
        35      35     500   numothersock
       107     107     500   numproc
         1       1     255   numpty
        31      31    2048   numsiginfo
        26      26     500   numtcpsock
    -----------------------------------------------
    Fail Count conditions: 2
    numproc 107 107 500 500 307
    numtcpsock 26 26 500 500 1
    I wonder why those numproc failcnts

  6. #6
    Join Date
    Dec 2004
    Location
    Butler,TN
    Posts
    2,413
    Hi!

    Ops! I missed that! Same thing...openvz recommends almost twice those as well.
    They have 500..openvz's example would allocate 800. Of course..as I said...ask the host first. Sometimes they will adjust it..sometimes they won't.

    I honestly believe many hosts have no clue what those numbers mean either...I think it's the truth sometimes. It took me quite some time to figure them out myself. In fact..a developer on openvz told me (and a reporter for Network Word)
    a bunch of things that were not true...just to be mean...I guess. ????

    Anyways...it's always best to explain the sitch to the host first..because some may realize the allocation is not really fair..and fix it.

    Bryon
    Bryon L Harvey
    Soil Relocation Engineer

  7. #7
    Join Date
    Jan 2006
    Posts
    582
    thanks to all for your comments, most helpful

    cheers

    Keith

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •