Wow! The performance has been improved a lot! Good job!
Comment has been collapsed.
Thank you for the continued support and improvements cg! ^ ^
Comment has been collapsed.
Hahaha, I almost had the exact same comment as you. Saw yours after typing mine :-)
Comment has been collapsed.
The one change you'll likely notice and dislike is the homepage no longer showing the total number of results
I really dislike it :_( I used to control the number of discussions created since this site don't let you check which are the new ones created/not read
Comment has been collapsed.
1 Comments - Last post 5 minutes ago by Peiperissimus
13 Comments - Last post 20 minutes ago by Peiperissimus
12 Comments - Last post 49 minutes ago by Pareidolistic
1,739 Comments - Last post 1 hour ago by steveywonder75
51 Comments - Last post 3 hours ago by gokugohanpan
16 Comments - Last post 3 hours ago by Arinojr
8 Comments - Last post 3 hours ago by wigglenose
670 Comments - Last post 4 minutes ago by minipac
9,348 Comments - Last post 13 minutes ago by minipac
306 Comments - Last post 19 minutes ago by Fluffster
77 Comments - Last post 45 minutes ago by Sakakino
104 Comments - Last post 1 hour ago by Williamatics
4,942 Comments - Last post 1 hour ago by masterbubu87
14 Comments - Last post 1 hour ago by Mortvie
Hi SG, as you might have noticed, we started running into slow load times last week during peak hours. We moved to a new host recently (AWS), and I setup our database on an instance with 122 GiB of RAM. This allowed our dataset and indexes to fit in memory, which solved a number of issues we experienced in the past couple of months as our database grew in size. Nonetheless, we've been hitting some limitations on the CPU side of things the past week, as seen here. The graph shows four days of CPU load on our database instance, and the waves represent the rise and fall of traffic during peak and off-peak hours. Once the instance reaches 100% load, we obviously see a sudden drop in performance as tasks begin to queue up.
I spent most of the past week better analyzing our traffic, and rolling out a wide variety of improvements. The one change you'll likely notice and dislike is the homepage no longer showing the total number of results. However, this is a needed change and one that's going to help us keep the load on the instance down. Other changes include adjustments to how the homepage results and featured giveaway are selected, and how winners and giveaway feedback are stored and retrieved. At the end of the day, you should notice the site being more responsive. The archive page will load twice as fast, the homepage will load 40% faster, user profiles, messages, and trades searches 30% faster, and individual discussions will load 15% faster. Other pages received some improvements as well, but the above are the ones you'll likely benefit from the most.
Overall, the performance is better than expected, and you can see the results here. As mentioned earlier, the blue line represents CPU load on the database during four days last week, and for comparison, the green line represents CPU load yesterday.
Comment has been collapsed.