I hear and understand your theory of tossing on RAM to fix the problem
.
I need a workaround for this very instant, not for a few weeks when I can get that in place. I can't have zero-postings for several weeks. I'm sure others might appreciate knowing if there are non-RAM solutions for a variety of reasons.
My research on InnoDB indicated that it would give me a speed boost. I found it definitely did on all of my forums. So I am very content with that change.
If that then requires some additional tuning, I am fine with that. Tuning is a part of life no matter what database one chooses.
In researching the specific error I get, I find that many people - even with giant amounts of RAM - hit the Query End error. The indicated solution in this specific case was to make this change to the my.ini file -
innodb_flush_log_at_trx_commit = 0
I have made that change on my lisashea server. I will report back in a few hours. That change seems logical given the reported error.
I'm still looking to find where that snippet of code is being called. I can't find it in the scripts directory.
