On that I agree with both of you
Some "unatural" positions are just because it is a snapshot of some movement, but in most cases it just looks wired and like a 3 year old tried to take his puppets apart. In the pictures above we can see both situations

I haven't only thought about the client. i know that the server side is what should matters. But imho i have in mind that somebody
told me that our root is configurated that the cpu & traffic of the gameservers have priority and the webcrap would be secondary.
Yeah something like QoS but in the vServer Software and not a Router. I am not sure who told me back in the days. But i am sure
that somebody told me this. Anyways you got your eye on the loadbalancer and so you know best how much the cpu & network
is used. but are we really in a situation where we have to save traffic? when the answer is yes - who steal our traffic? we got
lesser and lesser forum and mainpage hits day for day. also our gameservers idle 90% empty. when i host my site here on this
server there will be a lot more traffic. i think my pages will generate more traffic then the clanpage, forums, stats & fastdl together.
so i need to know before i put the domains on this server!


snapshots from a scene? how you got those ragdolls on the scene without possing? did they spawn and freeze themselves in those positions?
possing does not mean that the ragdolls on the scene can not be in movement or action. i don't know which movement they perform
on picture one but it must have something to do with heavily broken bones. picture two must be titled "3 combines need a wc, but no toilet around"
the css one or number three is really good. also your tf2 posse looks nice. but the first two - i don't know - but art is purely a matter of taste.

At the moment there is no really need to save bandwidth - but it will on times when gameservers are in more use.
You were right. There is some sort of load balancing / load priority on the virtual machines - but it controls cpu usage.
To control network load there has to be a packet filter in front of the hardware which tags network traffic with priority and limits bandwidth per protocol.

If you expect heavy traffic maybe it would be better to serve on another host.
I have no idea what kind of content you want to host. Maybe we should discuss this @ teamspeak next time.
Big files for download by mass of clients arent a good choice - this would cause lags on gameserver traffic.
Anyway its possible to limit bandwidth per client in the webserver but no one can tell how many clients are downloading.
On the other side - limiting number of clients is also not of choice - have you ever seen those crap webservers which display "server error 666: sorry dude, come back later, 17 clients are wanting data from me - so i'm unable to serve you at the moment".


Hehe you got the point.
I can do any of the positions showed on pic 1 with my own body :)
Except for the engy's left shoulder - there broke some bone of course ^^

When i'm looking again to the second pic applying what you said i can't get breath from laughing
The combines REALLY need some sort of toilet :>


LOL :)

yeah, i think this will be the best idea when we talk @ ts over that. i am planing to
install and config my webstuff over the xmas holidays so that i can go live in january.
i am thinking of hosting all the webcrap and db's here. the downloads and other traffic
hungry processes will be outsourced to the root server of a friend. i think when i outsource
most traffic except the mysqldb and the webstuff i can hold the traffic to a minimum.
but the best will be we have a talk about this when we meet next time on teamspeak.



don't laugh about my signature
it's the best sig in the world