| Mirage Source http://miragesource.net/forums/ |
|
| Multi-threading the server doable? http://miragesource.net/forums/viewtopic.php?f=201&t=3533 |
Page 1 of 1 |
| Author: | Asrrin29 [ Fri Mar 28, 2008 8:56 pm ] |
| Post subject: | Multi-threading the server doable? |
So My old server computer looks like it finally took a dump, leaving me with no good computer to run a dedicated server on when I finally get a beta client up and running. I am thinking about sinking $150 on a new mobo, proc, and memory, since I have a decent hard drive, case, and such. Only thing is even the cheapest of processors now-a-days are dual-cored, which got me to thinking. The server only uses one thread to process all the connections it handles and so is fairly linear. If I could somehow split things up in the server into multiple threads, a dual-core would make it much more efficient. Is multi-threading doable? if so, what is the best way to implement it? one thread for main game loop and one for winsock arrivals? or maybe one thread per client connection? I don't know, but I would like to get some answers, might be something worth taking a look at. |
|
| Author: | Lea [ Fri Mar 28, 2008 9:27 pm ] |
| Post subject: | Re: Multi-threading the server doable? |
It's definitely do able. You'd need to look at the windows API thread functions. It makes debugging a nightmare, and the VB6 IDE doesn't like it a whole lot... lots of crashes. |
|
| Author: | Asrrin29 [ Sat Mar 29, 2008 12:14 am ] |
| Post subject: | Re: Multi-threading the server doable? |
Yes, I've heard the VB6 IDE doesn't take to multi-threading well, but I would think it would be worth it if you have a very popular game with dozens, maybe even in the triple digits, of people conecting at the same time, multi-threading would allow the connections to get processed faster. |
|
| Author: | William [ Sat Mar 29, 2008 2:19 am ] |
| Post subject: | Re: Multi-threading the server doable? |
Quote: or maybe one thread per client connection Your kidding right? |
|
| Author: | Asrrin29 [ Sun Mar 30, 2008 2:21 am ] |
| Post subject: | Re: Multi-threading the server doable? |
William wrote: Quote: or maybe one thread per client connection Your kidding right? I have no idea, I'm new to anything to do with threads. I guess there would end up being a lot of threads on a per client basis. Maybe have three threads, one for the main loop, and two to handle connections? One for incoming one for outgoing? |
|
| Author: | Lea [ Sun Mar 30, 2008 3:03 am ] |
| Post subject: | Re: Multi-threading the server doable? |
Here's a good article on it: http://www.freevbcode.com/ShowCode.Asp?ID=1287 |
|
| Author: | Spodi [ Sun Mar 30, 2008 3:29 am ] |
| Post subject: | Re: Multi-threading the server doable? |
Asrrin29 wrote: William wrote: or maybe one thread per client connection Your kidding right? I have no idea, I'm new to anything to do with threads. I guess there would end up being a lot of threads on a per client basis. Maybe have three threads, one for the main loop, and two to handle connections? One for incoming one for outgoing?[/quote] (stupid quote block prevention) That would be pretty much the most basic kind of networking IO. Spawn a thread for each connection then do a blocking listen while sends are done in-line and also blocking (blocking isn't as much of an issue for sends). Its also probably one of the worst schemes for scalability. IOCP or asynchronous socket I/O would be a much better way to go. You could do your own thread pooling, but it'd become messy and troublesome very fast. The scheme I am working with now has a thread for the main loop: Code: While (true) UpdateWorld(); SocketManager.Heartbeat(); Sleep(); Loop UpdateWorld() would be self-explanitory. SocketManager.Heartbeat() tells all sockets to fork up their received data if they have any so it can be handled. It basically looks like: Code: HeartBeat() -> for every socket { Socket.Heartbeat(); } Socket.Heartbeat() { if (Socket.HasReceivedData) { OnReceive(); FlushReceivedDataQueue(); } } OnReceive() is an event trigger that the server is registered to. Its pretty much the same as calling the receive method, but through an event. Then the receive data queue is handled. This is still all in the update thread under the initial heartbeat() call. All data is sent with a header of their size to prevent packet fragmentation. Whenever a socket receives a callback from the async receive, the data is pushed into a receive buffer (just an array twice the size the maximum allowed send size). Then the receive buffer is searched through for completed packets, which is quick and simple with keeping track of the highest write position. Completed packets are pushed into the ReceivedDataQueue where they wait until the Heartbeat(). Sent data, if a send is not already in progress, is just sent. A boolean keeps track of if a send is in progress or not to prevent trying to send multiple times from a single socket. A send request is also called when the send finishes if there is any queued data to send. This allows for sends to happen pretty much as fast as possible without having to poll the socket. If a data send is already going and a send request is made, the data is used into a send queue. When the next in-progress send finishes, data is removed from the queue until either the queue is emptied or the buffered packet is full. This provides for a nice and easy buffering system. On a basic view, its a pretty simple system. Sends and receives are completely separated and, using a few locks (which unfortunately VB6 doesn't have so you'd probably have to do some kind of spin-wait, which sucks), theres no threading issues and you don't even have to think about threading when you're outside of the networking class. |
|
| Page 1 of 1 | All times are UTC |
| Powered by phpBB® Forum Software © phpBB Group https://www.phpbb.com/ |
|