Drocona Wrote:most servers are running 25000, no matter how big they are, although 30000 is the maximum available, you can use that too. 25000 = 25KB/s per player, 100tick slots will hardly get to 25KB/s at all.
Also I'm pretty certain you will have quite the trouble getting 20 slots @ 100 tick 
the above is pretty much wrong...
With more slots you'll need more rate this because the chance of more things happening at the same time increases, and the packet sizes with information to each client increases.
The average is usually lower a lot than 25k, but it is when the shit hits the fan so to speak, you need more juice.
Rate 25000 is an old value from 1.6 or something, but works decent for 10slot css war servers (although CAL uses max values of 30k and CB 35k now days).
Setting rate values too low will result in less packets per second received from the server when the packetsize*tickrate exceeds clients rate.
This is usually visible with net_graph on.
Best is to use net_graph 2 where you also can see packet sizes.
(On a tickrate 100 server 100 packet per second is transfered)
So
just do your math now.
Packet sizes * updates/sec = minimum rate needed ex. 400*100=40000)
(and i don't mean the average packet sizes, but some of the bigger ones at a reasonable value for online servers depending on bandwidth available etc.)
Max rate source can handle is 1mb/sek (rate 1048576) which should be used for example on LAN's for optimal hitreg.
And...
100 tick 20 slots not a problem, if you know what your doing apparently
