FPS doesnt go over 200

[Derek]

css Wrote:Is it always the Zombie mod server that is lagging?

Wouldnt be suprised.

[Derek]

dualcore1289 Wrote:a fps booster, changes the frequencies, and therefor boosts your fps. you can either open wmp and keep it running in the forground, or you can use the fpsbooster, which is located here, http://forums.srcds.com/attachment.php?aid=242 also, run that and leave it open in the forground.

LoL @ frequencies.

[deathamalation]

Its debian, the zombie mod server lags, probably a bad server to post an fps example of? ill post the stats of one of our scoutzknivez 12 slot servers while its empty if you want but youll still see under 200 fps....

I personally did not install debian onto the server. However if the kernel is that old, would it make a difference? should i upgrade?

Also

Code:

cat /etc/issue
Debian GNU/Linux 4.0 \n \l

And here is your picture..


EDIT: yes, obviously, its on dust2 at the moment.

[disco]

You realise that "apt-get update" only updates your package lists? If you want to upgrade your packages you need to do an "apt-get upgrade". this might actually solve some problems if you get an updated version of glibc

[deathamalation]

aspire-gaming:~# apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

[css]

I always compile my new kernels manually and install them manually. I don't like package managers

But, I read somewhere that Debian only installs new kernels on "apt-get upgrade" to /boot/, but it doesn't activate them. Take a look at /boot/ and /etc/lilo.conf. Then make a new entry to lilo.conf of similar vmlinuz-[kernel-version] than the others. Make the new kernel the default, so it will start the new kernel in reboot.

You're probably doing this the first time, and you're doing it remote. If something goes bad and the server doesn't reboot, there's nothing you can do. Some ISPs have very good rescue systems so you can reboot to the rescue system, fix the lilo.conf to reboot the old kernel and restart. Some ISPs have not-so-good rescue systems and you'll have to do all sorts of tricks to revert to your old kernel (usually problems are that devices at /dev/ are not in the same order, or lilo writes the boot loader to wrong place, etc...). Grub (alternative boot loader) is bit more difficult to configure, but it's better because it can read config file on-load and doesn't mix harddrive devices because it looks at their unique IDs instead of the primary/secondary and/or cable order.

I recommend you don't start to do this by yourself. You risk making your system unbootable and you could end up having to pay-by-hour for your ISP to get the old kernel reverted. At least make sure you've got good plan what you're going to do when your server doesn't reboot. I speak of experience

[ClanWoof]

[quote recommend you don't start to do this by yourself. You risk making your system unbootable and you could end up having to pay-by-hour for your ISP to get the old kernel reverted. At least make sure you've got good plan what you're going to do when your server doesn't reboot. I speak of experience[/quote]
Be careful as he says I have had issues with one of my servers when updating the kernel not fun if something goes wrong. If you have other questions about it ask on here or on the Debian forums.

[deathamalation]

To late, been there done that, didnt work haha, i used grub though so i made it so it only tried loading that kernel once, then it reverted back to the old one if it didnt work on a second restart. just had to get the host to restart.

maybe a change in os?

[css]

If you already once succeeded bringing your unbootable system back online, then I'd say you're quite safe trying out more kernels.

I'm not sure how you compile the kernel and how do you do install process, but I do it always manually, which is semi-easy from start to beginning.

I would experiment with other kernels. Do "make oldconfig" or use "/usr/src/linux/scripts/extract-ikconfig" (you have to start it from /usr/src/linux/ directory) to extract the current kernel config from your active kernel. Then do "make menuconfig" and go change 1000 Hz, desktop level pre-emption and maybe do other tweaks that you've heard rumours that would make your server faster.

You spoke about change of OS. Do you mean BSD or Windows I wouldn't change - not even the Linux distro. Kernel does it all.

[CarVac]

If you use ubuntu, (maybe debian, too) when you install a kernel there remains the grub entries for the old kernels if your new one doesn't work. That comes in a LOT of handy.

[css]

We talked with deathamalation via Steam. Obviously he's got dedicated server on which he doesn't have direct access. That's why having old kernels in the cool looking boot menu list doesn't do any good because he doesn't see the server until SSH starts on the server. Also the ISP doesn't have good remote control systems, so everything should go bulls-eye on the first try.

I recommended doing plain "make oldconfig" (or taking the same config from "zcat /proc/config.gz") and then compile the new kernel with the same configs. That should be somewhat reliable way to get a custom compiled kernel running and verify that the kernel is truly working. Then after having the custom kernel it's possible to start making changes to the kernel. I suggested enabling CPU specific optimizations (stock kernels have only "general" optimization) and disabling all references to CPU frequency scaling etc.

We'll see how deathamalation succeeds in this. It's a difficult task, which is tough piece even for experienced server admin.