my server is laggy

[EdwardTobia]

to reduce choke u need to up the sv_maxrate and/or lower tickrate.
I see that you are running a 66 tick server, i would suggest using 33 tick or if u have a really good upload speed then use 50tick, no more.

[hexitnow]

Sorry ED but I gotta say this. Thats kind of jumping to conclusions. How many slots are you running BADASS. If you are running less than 18 you can run 66 or higher as long as you have the bandwidth and processor to cope. 1.5 MPBS isn't a small amount, but it's alot more then most home server have. To help the choke you can lower the tickrate, like ed said. If you raise sv_maxrate Im pretty positive it's gonna make it worse, as the clients will be using more bandwidth compared to if it were a lower number. Tomorrow I will post my exact rates, you can use them, and I run 0 choke 24/7 with 1024 KBPS. Here is a page I learned alot about tickrates and rates. Should help you as I learned from this.
http://forums.srcds.com/viewtopic-tid1094-high-tickrate-and-rate-srcds-faq
Hope all goes well and I will post my rates tomorrow. Try running a 33 tick and see how the choke goes after that.

[BADASS]

I am running 16 slots and I got unlimited bandwidth and my processor only runs at 15%-35% CPU usage with the server on

[hexitnow]

Hmm, my suggestion is start messin with the rates. It's hard to make a good guess without being there at your comp. I would change them little by little until u get something you like. Although I would change the tic to 33. I tried 66 with my rates last nite and choke went up.

[Drocona]

This should give you a good idea what to do:

high choke means: not enough bandwidth or too low rates
explanation: choke means the amount of packets in line to the server, this means they have to wait to arrive. If you limit your BW by setting the rates too low you will get choke because the tickrate wants and DOES send more, but the rate limit won't allow it so the packets get inline and wait for their turn.

So when choke starts killing you, you up the rates (sv_maxrate) to allow more to pass. If your rates are maxed (unlimited) and choke starts to show, it means your out of bandwidth (you're using the full 1.5Mbps). In this case you set the tickrate a bit lower and try again till you have the maximum quality you can get.

[hexitnow]

Thanx for clarifying that dro. Havent seen you on in awhile.

[Drocona]

Yeh I upgraded my PC friday, did a full format with it, couldn't come online then, saturday I had a LAN-Party with my friends, Sunday was busy day and now I got the chance to post a bit again

[hexitnow]

Good to have you back

[Drocona]

Thnx, there have been a shitload of posts tho O_o

never seen it so busy over here
goin to bed now, cya ppl tomorrow

[BADASS]

I put the tickrate down to 33 and the choke went up higher

[hexitnow]

when u changed the tickrate did u also change the sv_minupdaterate and sv_maxupdaterate, they have to match what the tickrate is.

[BADASS]

yea I changed that also

[hexitnow]

Are you running the server and playing CSS on the same machine?

[BADASS]

yes

[hexitnow]

When you join is when the choke is going up. I had the same problem on mine when I ran my server and played CSS on the same machine.