Big Performance Issue

Discussion in 'Bukkit Help' started by crashr, Sep 24, 2012.

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

    crashr

    Hi all,
    I wanted to know if it is normal that running a vanilla server use like 1% of my CPU and running CraftBukkit use 25% of my CPU even if there is nobody connected and no plugins installed ? Why CraftBukkit need to use so much Ghz when nothing happen on the sever ? cs:go or Bf3 servers don't use as much cpu. I have intel i7 850 with 12go of ram gskill.

    1. What OS are you using ? win7
    2. What architecture is the OS you are running ? x64
    3. What version and architecture is your java install? 1.6.0_35
    4. Are you running any wrappers? McMyAdmin, mcadmin, Hamachi, etc? no
    5. What build of CraftBukkit are you running? i tried both 1.3.1-R2.0 and 1.3.2-R0.1

    6. What command are you using to run your CraftBukkit server?
    javaw -Xmx1024M -Xms256M -jar H:\minecraft\craftbukkit.jar nogui

    7. What plugins are you running? no plugin
    8. What error are you getting (post your server.log file)? no error

    Ok i finally found why CraftBukkit take 25% on my CPU => it is because i started it with javaw.exe and not java.exe .
    javaw is something like the windowed version of java. When i launch vanilla with javaw the performance is the same then lauching it with java. I don't know why when i start craftbukkit.jar with javaw and not java there is a big CPU issue.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 28, 2016
  2. So you can actually set up bf3 server on your own PC?
    Am I that uninformed ?!
     
  3. Offline

    TnT

    Try this command:
    java -Xmx1024M -Xincgc -jar H:\minecraft\craftbukkit.jar
    Note this is not javaw, but rather java.

    If you still see large CPU usage, try:
    java -Xmx1024M -Xincgc -jar H:\minecraft\craftbukkit.jar -nojline

    Also, I do hope that H: drive is a local drive, not a smb share.
     
Thread Status:
Not open for further replies.

Share This Page