Increasing server RAM trouble..

Discussion in 'Bukkit Help' started by ONI Ricky, Oct 27, 2013.

Thread Status:
Not open for further replies.
  1. Offline

    ONI Ricky

    I host a bukkit server on my own machine and am experiencing difficulties trying to increase the amount of RAM my server runs on, I'm not a computer wiz but I know a fair amount so I apologize ahead of time for stupid questions. Here we go..
    I have 8 GBS of RAM on my computer
    I run 64 bit java
    Have a 64 bit Windows 7
    My run script:
    java -Xms1024M -Xmx3072M -jar ONI.jar
    @PAUSE
    The problem is, when I do the /mem command it says I am only running on less than a GB of RAM, and I can also tell that its definitely not running on anything near to 3 GBs.
    Any help is much appreciated!
     
  2. Offline

    vemacs

    Your minimum heap is 1GB. It'll scale up to 3GB when needed. Don't worry.
     
    TheMcPlayer1997 likes this.
  3. Offline

    ONI Ricky

    I don't think so... Sometimes we can get pretty bogged down with lag with big w.e. and what not and it seems like the RAM stays the same.
     
  4. Offline

    vemacs

    Lag has almost nothing to do with heap allocation/usage.
     
  5. Offline

    ONI Ricky

    Is there anyway I can change my minimum heap?
     
  6. Offline

    LHammonds

    If doing W.E. changes is causing issues (any large selections will), you might want to look into something like SafeEdit. Be aware that the undo is replaced with the safe undo (sundo) which is only usable by someone with OP access. That function does not have a permission node (yet).
     
  7. Offline

    ONI Ricky

    I was using it as an example, I understand that massive w.e. will slow any server down and my server has no specific issue with w.e. I just wanted to provide an example of a bogged down server.
     
  8. Offline

    LHammonds

    Look into NoLagg and ClearLagg. I posted examples on how to use them for performance testing and identifying problem areas using those tools.

    Link to Post
     
Thread Status:
Not open for further replies.

Share This Page