Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
I've now reverted step 1 of what I did to try to fix it. I'd like to have confirmation again at this point from a couple of members that new posts are performing as intended, before I revert the final stuff in step 2 from the search-specific exclusions I implemented.
Going slow on the reversion to ensure we get it right.
I had 5 "New" post buttons to check, and it turns out that I had visited all five threads recently, so when I pressed the New buttons, I could recognize the last post in each that I had seen before. In each case, it came to the post directly after the one I had previously seen, as it should have.
Thanks @bobwest. I've now also reversed the changes I made to the search queries. So now it was just the simple nginx fix, that's all that is in place, for the 'new' posts. Let's see if it still works this way, or if the search query exclusions are necessary.
Added a small bit of failover code so that if a backend service is unavailable for a few seconds (switching to another server, restarting a service, etc) it should stop generating user-facing error messages or cause disruptions with pages not loading.
I believe I corrected the issue with the site polls. After the migration, the polls were showing out-of-date information due to a caching scheme error. I corrected this by disabling caching in the site polls module.
As of this post, I've re-enabled caching within this module. Please keep an eye on the site polls for any odd behavior.
To be clear, the current site poll is still "Expectations vs Reality: Trading Profitability (choose two options)" and will remain so for a few days more at least, so if you are seeing anything other than that option -- please report it.
Also, I am looking for anyone who has not yet voted to please check the vote count prior to voting, then cast your vote, then check the count again. Since this poll asks for two votes to be cast, it should increase by two.
I would call this an improvement in site performance, right guys? Can you spot the migration spike (lol)... what a difficult few days.
How does the site feel to you now? Faster than before the migration?
I realize that submitting posts is still slower than before. This is mostly due to a multi-master Galera server config, which requires all servers be in sync before acknowledging the SQL write has been processed.
But I am looking for ways to improve performance by re-writing some of the queries, I just need more time.
Other than that, as far as page load performance, let me know your thoughts. And we're still making improvements and have much more scalability now to do it than before.