You say you don’t think it will solve all the problems, so what problems
will it definitely solve and what problems will remain?
This move would help in having more resources, but having more resources
would not solve concurrency related problems (Fetching same data at the
same time). Instead of correcting the poor application design, decision
makers (Developer turned Architects) are expecting the scaling to solve
these problems.
On Thu, Apr 5, 2018 at 5:23 PM, Andy Sayer <andysayer@xxxxxxxxx> wrote:
If the problem to be solved is purely one of performance it’s probably
worth making sure you’re not missing something obvious in your current
setup.
With proper instrumentation, it should be simple enough to see where the
time is going for these important processes and see if there is a way to
eliminate work/make it faster. Once you do this you will also know how much
work would be involved in implementing the change and how much it would
improve things.
You say you don’t think it will solve all the problems, so what problems
will it definitely solve and what problems will remain?
If the move to Inno-DB is a guess at improving performance because it has
“scalability” then don’t be surprised if nothing changes.
Regards,
Andrew
