Not sure why this will not work for Logos every time there is a website upgrade
Bring down the DR Upgrade the DR to the new website Switch over to DR Bring down the primary Upgrade the primary Bring the primary back up Not sure why this will not work for Logos every time there is a website upgrade
My guess it that the problem is not with the code that renders the website, but rather the scalability between the front-end website and the database that contains the information about the products own by any user. Given that all the product structures have changed, I imagine that the comparisons of an individual user's current packages and any new packages needs to be created on the fly. There will be not previously-cached results. Consequently, a heavy load on the system.
Just a crazy, completely uninformed guess.
Agape,
Steve
My guess it that the problem is not with the code that renders the website, but rather the scalability between the front-end website and the database that contains the information about the products own by any user.
This is my suspicion as well. Any modern web server on moderate hardware can handle the loads FL's entire customer base could throw at it. Someplace in the architecture is a shared resource which is being overwhelmed by the volume of web requests.
Donnie
I suspect a database technology beloved by a key influencer that is limited in its scalability.
