Quote:
Originally Posted by manulaiko3.0
"Premature optimization is the root of all evil"
Instead of worrying about nonexistent problems, worry about making it work.
|
I dont think that you should worry at all. Making it work is not very hard, it only costs a lot of time.
From my point of view programming clean from the beginning is the best Solution. In case of servers most of them did not have a lack of "not working", but rather a lack of security and performance.
Quote:
Originally Posted by NUMANDERBUHMAN
Actually I've put way more effort into performance than I've actually put into easy to read but if coded right it should both be easy to read and solid performance.
I'm handling the clients using a loop and tick each and every one of them per x ms. I didn't bother playing with threads and await but I've used it on a few places. I'll have to do a proper stress test soon to check if everything is as good as I hope it is.
|
C# provides good features to implement easy to read algorithms, for example with Linq and the new things with C# 6.0, but performance is something not as easy as algorithms. Therefore I am asking you.
So you are having a "MessageFifo" containing for example movement stuff, etc.
Every x ms you clear that loop and send everything to the clients ? Or did I missunderstood that part.
In case of the ms ? Are you using 8ms each or just a random value ?
I am really interested in those things. I used to program my own pserver for friends, but nowadays I rarely have time for software programming ;-)
best regards,