Possible downtime soon for server upgrade
Hi all,
Just a heads up that there may be some downtime over the next day or so, as I'm migrating the website to a new server with more storage. Hopefully the downtime will be minimal (less than one hour in total) and there are no unexpected issues (touch wood!).
Teeb
4
replies
1775 views
Description
Hi all,
Just a heads up that there may be some downtime over the next day or so, as I'm migrating the website to a new server with more storage. Hopefully the downtime will be minimal (less than one hour in total) and there are no unexpected issues (touch wood!).
Teeb
Just a heads up that there may be some downtime over the next day or so, as I'm migrating the website to a new server with more storage. Hopefully the downtime will be minimal (less than one hour in total) and there are no unexpected issues (touch wood!).
Teeb
Can be used to make Runewords:
Answered•Go to post
The server migration is now complete! 
diablo2.io now running on a new machine:
The main reason for the server migration was due to storage - we kept on capping out at about 240GB/240GB on a weekly basis. I had cronjobs running to purge the cache every week in order to free up space, but of course that was only a temporary stopgap until a machine with more disk space could be provisioned. With more permanent attachments like screenshots in holy grail records (of which there are 50k now), just couldn't keep the disk usage down any longer.
Now we have 480GB so plenty of room. There's further work to be done on reducing the amount of files building up in the cache in the first place (one of the biggest culprits of growing disk usage over time) besides just purging it weekly.
We were averaging about 10-20% CPU usage on the old server recently, so didn't need as much processing power for the new one and opted for six cores instead of twelve. In fact, the site has been using a very CPU-overpowered server for over two years now - mainly because at the start of the site's life the code was really awful and not performant at all, meaning that I had to stand up more powerful hardware to brute-force the shit code to work for all the initial users. Performance has improved since then meaning the additional CPU cores were unnecessary.
Monitoring consumption today (with about 2000 concurrent users at any time), we're at about 5-15% total CPU usage on the new server. This is lower consumption than the old one (despite having less cores) because the processors on the new server are more modern. I also spent some time this morning optimising various slow SQL queries - SQL is the biggest consumer of CPU for d2io, so any performance increase here means less CPU usage overall.
RAM is always (and has always been) using about 3GB of the 16GB available and is fairly steady. Someone here probably knows more about what the machine is usingthe RAM for in the first place - I have no idea lol but it's not a problem at the moment and never has been for the running of the site. I think RAM is more important for single page applications and javascript-first websites of the modern era, not so much for PHP.
Was a ballache to get everything migrated across and configured correctly - but I'm satisfied with the new set up. If you guys get any serious slowdowns or hiccups please let me know in here and it will help me diagnose and fix if needed. I will be keeping the old server live for another day or so just in case we need to move back to it in a hurry for whatever reason.
diablo2.io now running on a new machine:| Old server | New server |
|---|---|
| 12 CPU cores | 6 CPU cores |
| 240GB SSD | 480GB SSD |
| 16GB RAM | 16GB RAM |
Now we have 480GB so plenty of room. There's further work to be done on reducing the amount of files building up in the cache in the first place (one of the biggest culprits of growing disk usage over time) besides just purging it weekly.
We were averaging about 10-20% CPU usage on the old server recently, so didn't need as much processing power for the new one and opted for six cores instead of twelve. In fact, the site has been using a very CPU-overpowered server for over two years now - mainly because at the start of the site's life the code was really awful and not performant at all, meaning that I had to stand up more powerful hardware to brute-force the shit code to work for all the initial users. Performance has improved since then meaning the additional CPU cores were unnecessary.
Monitoring consumption today (with about 2000 concurrent users at any time), we're at about 5-15% total CPU usage on the new server. This is lower consumption than the old one (despite having less cores) because the processors on the new server are more modern. I also spent some time this morning optimising various slow SQL queries - SQL is the biggest consumer of CPU for d2io, so any performance increase here means less CPU usage overall.
RAM is always (and has always been) using about 3GB of the 16GB available and is fairly steady. Someone here probably knows more about what the machine is usingthe RAM for in the first place - I have no idea lol but it's not a problem at the moment and never has been for the running of the site. I think RAM is more important for single page applications and javascript-first websites of the modern era, not so much for PHP.
Was a ballache to get everything migrated across and configured correctly - but I'm satisfied with the new set up. If you guys get any serious slowdowns or hiccups please let me know in here and it will help me diagnose and fix if needed. I will be keeping the old server live for another day or so just in case we need to move back to it in a hurry for whatever reason.
The server migration is now complete! diablo2.io now running on a new machine:
The main reason for the server migration was due to storage - we kept on capping out at about 240GB/240GB on a weekly basis. I had cronjobs running to purge the cache every week in order to free up space, but of course that was only a temporary stopgap until a machine with more disk space could be provisioned. With more permanent attachments like screenshots in holy grail records (of which there are 50k now), just couldn't keep the disk usage down any longer.
Now we have 480GB so plenty of room. There's further work to be done on reducing the amount of files building up in the cache in the first place (one of the biggest culprits of growing disk usage over time) besides just purging it weekly.
We were averaging about 10-20% CPU usage on the old server recently, so didn't need as much processing power for the new one and opted for six cores instead of twelve. In fact, the site has been using a very CPU-overpowered server for over two years now - mainly because at the start of the site's life the code was really awful and not performant at all, meaning that I had to stand up more powerful hardware to brute-force the shit code to work for all the initial users. Performance has improved since then meaning the additional CPU cores were unnecessary.
Monitoring consumption today (with about 2000 concurrent users at any time), we're at about 5-15% total CPU usage on the new server. This is lower consumption than the old one (despite having less cores) because the processors on the new server are more modern. I also spent some time this morning optimising various slow SQL queries - SQL is the biggest consumer of CPU for d2io, so any performance increase here means less CPU usage overall.
RAM is always (and has always been) using about 3GB of the 16GB available and is fairly steady. Someone here probably knows more about what the machine is usingthe RAM for in the first place - I have no idea lol but it's not a problem at the moment and never has been for the running of the site. I think RAM is more important for single page applications and javascript-first websites of the modern era, not so much for PHP.
Was a ballache to get everything migrated across and configured correctly - but I'm satisfied with the new set up. If you guys get any serious slowdowns or hiccups please let me know in here and it will help me diagnose and fix if needed. I will be keeping the old server live for another day or so just in case we need to move back to it in a hurry for whatever reason.
This post was marked as the best answer. diablo2.io now running on a new machine:| Old server | New server |
|---|---|
| 12 CPU cores | 6 CPU cores |
| 240GB SSD | 480GB SSD |
| 16GB RAM | 16GB RAM |
Now we have 480GB so plenty of room. There's further work to be done on reducing the amount of files building up in the cache in the first place (one of the biggest culprits of growing disk usage over time) besides just purging it weekly.
We were averaging about 10-20% CPU usage on the old server recently, so didn't need as much processing power for the new one and opted for six cores instead of twelve. In fact, the site has been using a very CPU-overpowered server for over two years now - mainly because at the start of the site's life the code was really awful and not performant at all, meaning that I had to stand up more powerful hardware to brute-force the shit code to work for all the initial users. Performance has improved since then meaning the additional CPU cores were unnecessary.
Monitoring consumption today (with about 2000 concurrent users at any time), we're at about 5-15% total CPU usage on the new server. This is lower consumption than the old one (despite having less cores) because the processors on the new server are more modern. I also spent some time this morning optimising various slow SQL queries - SQL is the biggest consumer of CPU for d2io, so any performance increase here means less CPU usage overall.
RAM is always (and has always been) using about 3GB of the 16GB available and is fairly steady. Someone here probably knows more about what the machine is usingthe RAM for in the first place - I have no idea lol but it's not a problem at the moment and never has been for the running of the site. I think RAM is more important for single page applications and javascript-first websites of the modern era, not so much for PHP.
Was a ballache to get everything migrated across and configured correctly - but I'm satisfied with the new set up. If you guys get any serious slowdowns or hiccups please let me know in here and it will help me diagnose and fix if needed. I will be keeping the old server live for another day or so just in case we need to move back to it in a hurry for whatever reason.
If SQL is on the same server, then the RAM will be used by the database application (mariaDB, PostresQL, whatever). Having enough RAM to keep active parts of the database in Memory means that you dont need to read from disk as much, which speeds up selects. Between cache at the app level, and then just OS level caching, having enough RAM helps avoid becoming Io constrained
It is on the same server - I will look into tweaking the config to leverage more of the available RAM and see if that speeds up SELECTs some more. Thanks for this information!
It will only speed them up if you are hitting disk to read data. But yes, Memory tuning of database servers is important for performance, along with ensuring you have the right indexing set up
Similar pages
Advertisment
Hide ads
Greetings stranger!
You don't appear to be logged in...
bbb0
Bertram The Cursed
Kavatch2
mojoed1No matches
Teebling
9560Admin