0
Since, the donation drive, we've been able to deploy extra servers to help handle the load. I Forge Iron now uses multiple servers around the world, or a Content Delivery Network, to host static items like images. This network also means we're on 26 servers closer to you, where ever you are.
Since April 12th, we've reduced the load time of I Forge Iron by 60%.
Another problem is the amount of pages we serve out. During peak hours, I Forge Iron, has been maxing out it's resources or Load. In other words, too many people at once. Here's a server load graph, which is powered by the new server.
We're now at around ~30% load, which is excellent. The memory is at 50% because we now cache (store) commonly used pages in the memory, reducing the read/write cycles to the hard drive. The Content Delivery Network (CDN) also has reduced a significant portion of our load.
Now the site is zippier and more responsive, we'll be turning our focus towards content and expansion.
Since April 12th, we've reduced the load time of I Forge Iron by 60%.
Another problem is the amount of pages we serve out. During peak hours, I Forge Iron, has been maxing out it's resources or Load. In other words, too many people at once. Here's a server load graph, which is powered by the new server.
We're now at around ~30% load, which is excellent. The memory is at 50% because we now cache (store) commonly used pages in the memory, reducing the read/write cycles to the hard drive. The Content Delivery Network (CDN) also has reduced a significant portion of our load.
Now the site is zippier and more responsive, we'll be turning our focus towards content and expansion.
Mark<><