Would using view frustrum culling benifit players fps performance in a multiplayer game?

Has anyone tried it with say 100 players and only render the players that are within a set radius from you ? but for all the other players you would still need to know about there x,y,z positions right so the server always sends there positions to you that make the client decide if they should be rendered or not.

Could you do this for terrain and geomtry as well or that that be expensive on the server?

i couldn't imagine NOT doing it! i mean you're already massively multi-player, with network lag and overhead slowing you down, so you start out with two strikes against you vs a single player title. AND YOU DON"T CULL THE SCENE? obviously, you'll still need all entity data, but physics and graphics should be unrelated, except for the fact that they both use the entity's location and rotation to do their job.

I'd just add that frustum culling is purely a graphical task, and should be done client side and not on the server. Culling shouldn't have any effect on the amount of data you're sending, since you're presumably going to be sending the positions of each player either way.

Also, frustum culling terrain and static objects can be expensive if you've got large and detailed maps, so ideally you should have some kind of quad tree structure to limit the number of checks you need to do, but in the end any kind of culling is going to be much less expensive than attempting to draw all the off-screen assets.