1
Wish list / More Scalable Server Query
« on: January 22, 2004, 10:09:20 am »
I notice that right now, the server status page uses PHP to perform a server query at port 13333. From previous experience I feel that using PHP to perform queries dynamically is not going to be a good idea in high-traffic scenarios.
What I suggest is that Port 13333 only listen to local queries, and that a script that generates a static HTML page concerning the server status of PlaneShift be done instead. The script could be run every minute, with the HTML file included in pages such as this forum, and on planeshift.fragnetics.com
I have a few reasons for this:
1) In high-traffic scenarios the web-server is not going to be able to handle requests efficiently. We noticed this during the times when we were Slashdotted in 2002 and 2003. We decided to make our webpages static as far as possible to prevent this from happening again in future.
2) This prevents possible DoS attacks on port 13333. I\'m not sure if the main PlaneShift port can be attacked easily, but limiting the queries to local users or a restricted list of remote users seems like an ok idea to me.
3) Overall decreased load on the PS Server, which listens to the query port at 13333 apart from running the main PlaneShift game itself. Our web server would also become slightly more responsive.
I see 3 simultaneous connections to the query port this moment.
Devs what do you think?
What I suggest is that Port 13333 only listen to local queries, and that a script that generates a static HTML page concerning the server status of PlaneShift be done instead. The script could be run every minute, with the HTML file included in pages such as this forum, and on planeshift.fragnetics.com
I have a few reasons for this:
1) In high-traffic scenarios the web-server is not going to be able to handle requests efficiently. We noticed this during the times when we were Slashdotted in 2002 and 2003. We decided to make our webpages static as far as possible to prevent this from happening again in future.
2) This prevents possible DoS attacks on port 13333. I\'m not sure if the main PlaneShift port can be attacked easily, but limiting the queries to local users or a restricted list of remote users seems like an ok idea to me.
3) Overall decreased load on the PS Server, which listens to the query port at 13333 apart from running the main PlaneShift game itself. Our web server would also become slightly more responsive.
I see 3 simultaneous connections to the query port this moment.
Devs what do you think?