Announcement

Collapse
No announcement yet.

qwsv running at 100% CPU!

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    qwsv running at 100% CPU!

    Ok I know I'm insane to have even tried qwsv on a 'modern' Linux system, but I built the source, and it runs at 100% CPU....

    So what do people use to host a quakeworld server...??

    And I'm assuming it won't run 100% cpu!
    Tags: high cpu, qwsv
  • #2
    not with todays hardware, it will laugh at a quakeworld server,or a netquake server for the matter.

    probably windows. Windows makes like easier when it comes to gaming.
    Want to get into playing Quake again? Click here for the Multiplayer-Startup kit! laissez bon temps rouler!

    Comment

    • #3
      I use the debian distro for my netquake servers in europe and my server in usa runs on windows.
      The bigfoot server in europe also runs the netquake server on debian even the quakeworld server.

      Most of my servers run at 1-3% in idle and with people on at 10%+- .
      Only my darkplaces server runs at 20-30% but that is on a pII 450mhz



      Send from iphone.
      My servers for the gamers:
      bigfoot.servequake.com / damage.servequake.com
      port 26000 EuroQuake
      port 26001 EuroQuake Coop

      newyork.quakeone.com
      Offline ATM
      fvf.servequake.com
      flanders.servegame.org / flanders.servequake.com
      Offline ATM
      newdm.servequake.com
      port 26010

      http://bigfoot.servequake.com (EuroQuake)
      sigpic

      Comment

      • #4
        found it

        get this, if I run it via screen ... it'll run at max 1% ...

        nohupping the thing makes it go berserk!

        Comment

        • #5
          aye, nohup will make it wake up too much. any decent custom port should have that fixed. fteqwsv or mvdsv should both be fine, I hope...
          there are a lot of security issues with vanilla quakeworld, so you probably don't want to run it anyway.

          quakeworld is meant to wait on some sockets until it receives a packet, at which point it wakes up and does its stuff. it also waits for keyboard input so you can type stuff. using nohup on certain system (debian but not suse, for example) can result in the 'select()' system call returning instantly, every single time, so the server never idles properly.
          who wants a server you can't interact with anyway? :/
          Some Game Thing

          Comment

          • #6
            Originally posted by Spike View Post
            aye, nohup will make it wake up too much. any decent custom port should have that fixed. fteqwsv or mvdsv should both be fine, I hope...
            there are a lot of security issues with vanilla quakeworld, so you probably don't want to run it anyway.

            quakeworld is meant to wait on some sockets until it receives a packet, at which point it wakes up and does its stuff. it also waits for keyboard input so you can type stuff. using nohup on certain system (debian but not suse, for example) can result in the 'select()' system call returning instantly, every single time, so the server never idles properly.
            who wants a server you can't interact with anyway? :/
            Ok that makes perfect sense!!!! Thanks for the explanation!

            Comment

            Previous template Next
            Working...
            X