Results 1 to 6 of 6
  1. #1
    Join Date
    Sep 2002
    Posts
    78

    VPS Specs and RAM handling - need advise

    I am currently on a VPS which has 384 MB of RAM and I am having some kind of RAM shortage.

    VPS specs are;
    Windows 2003
    Plesk 7.6 for Windows
    MySQL 5
    mailenable
    tom cat
    (cannot think of anything else using serious RAM)

    I am using external shared MSSQL, no AV running inside the VPS.

    I have currently have 10 - 15 live web sites.
    2 of them using MSSQL, 2 of them MySQL and 2 of them Access DB.
    The biggest DB is around 10 or 15 MBs and other are around 2 to 5 MBs.

    Only one (using MSSQL) has considerably heavier traffic (around 3 GB traffic and around 150k page views per month).
    Second closest has around 1,5 GB monthly traffic, and drops by less than a Gig on the others..

    But from time to time SMTP stops working or AWStats scheduler is having trouble to generate statistics. I am told that this is all about low RAM.

    So what you think? Is 384 MBs of dedicated RAM is not enough for this?

    What would the optimum amont of RAM in this case?

    And of course things will grow in time, so the load will get heavier (maybe a forum will be added or a CMS).
    How can I calculate the RAM needs, before it becomes a problem?

    I have read a lot of Linux configuration threads here on WHT but what about on Win 2003? Is there anything I can do to optimise RAM usage (a good reading link would be great on this one).

    Any comments would really be appriciated...
    Just fooling around...

  2. #2
    Quote Originally Posted by maxxkin
    Is 384 MBs of dedicated RAM is not enough for this?
    I think enough

  3. #3
    Join Date
    Dec 2004
    Location
    Butler,TN
    Posts
    2,413
    Hi!
    I would advise shutting down tomcat...and see if this is the problem. I expect it is. Tomcat has a very bad habit of being a resource hog...even using resources it doesn't need. The only place I've seen it behave is on a vps..nothing else on the vps..just tomcat. Even then...what I've used is not straight tomcat..it is IBM Application Server..and works well in a server with your specs..but nothing else.

    Bryon
    Bryon L Harvey
    Soil Relocation Engineer

  4. #4
    Quote Originally Posted by maxxkin
    I am currently on a VPS which has 384 MB of RAM and I am having some kind of RAM shortage.

    VPS specs are;
    Windows 2003
    Plesk 7.6 for Windows
    MySQL 5
    mailenable
    tom cat
    (cannot think of anything else using serious RAM)

    I am using external shared MSSQL, no AV running inside the VPS.

    I have currently have 10 - 15 live web sites.
    2 of them using MSSQL, 2 of them MySQL and 2 of them Access DB.
    The biggest DB is around 10 or 15 MBs and other are around 2 to 5 MBs.

    Only one (using MSSQL) has considerably heavier traffic (around 3 GB traffic and around 150k page views per month).
    Second closest has around 1,5 GB monthly traffic, and drops by less than a Gig on the others..

    But from time to time SMTP stops working or AWStats scheduler is having trouble to generate statistics. I am told that this is all about low RAM.

    So what you think? Is 384 MBs of dedicated RAM is not enough for this?

    What would the optimum amont of RAM in this case?

    And of course things will grow in time, so the load will get heavier (maybe a forum will be added or a CMS).
    How can I calculate the RAM needs, before it becomes a problem?

    I have read a lot of Linux configuration threads here on WHT but what about on Win 2003? Is there anything I can do to optimise RAM usage (a good reading link would be great on this one).

    Any comments would really be appriciated...
    Greetings,

    Does this VPS have any burstable memory?

    <<Signature to be setup in your profile>>
    Last edited by anon-e-mouse; 10-20-2006 at 08:48 PM.

  5. #5
    I see you are running tomcat.

    Also, I would like to mention java can be a considerable memory hog without strict limitations.

  6. #6
    i was thinking perhaps the MSSQL could be hogging memory....

Posting Permissions

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