Conversation
Notices
-
@hannes2peer if you have tweaked your mysql instance , could you share your config in patebin or something simular?
- Roland Häder likes this.
-
@knuthollund @hannes2peer I can share mine (without paths and credentials): https://social.mxchange.org/file/config.txt for download and https://social.mxchange.org/file/config.phps for viewing.
-
@roland great tx! @hannes2peer
-
@roland hmmm was more thinking of the config for mysql db (daemon). /cc @hannes2peer
-
@knuthollund we haven't really. during the german twitter strike i tried a few things, but nothing made any difference.
-
@knuthollund > apart from increasing qd threads. but i'll tell you if i find something :)
-
@knuthollund @hannes2peer More memory and caching is always good in /etc/mysql/my.cnf (oh, and using #MariaDB of course makes it all less Oracle and more cool)
-
@mmn i think i have to hunt for un-indexed queries also. phpmyadmins's diagnostics tool says there are lots of those
-
@knuthollund @hannes2peer @mmn Mine: https://social.mxchange.org/file/my.cnf
-
@knuthollund @mmn i followed @roland's example and disabled OpportunisticQM and Cronish now. was that a good idea? can't tell any difference
-
It's irrelevant to disable those to increasing performance. The margins are infinitesimal. It's much worse for the DB server to do a cross-table lookup even using properly indexed keys. Especially when running as #Quitter does, OpportunisticQM is probably just beneficial. Cronish doesn't do anything right now - at all - but will be useful for polling non-PuSH feeds in the future.
-
@mmn ok, i'll enable them again :) thanks!
-
Please keep in mind that #query-cache is an out-dated feature as it doesn't really help you much.
-
@mmn Hmm, I have read it that both are not needed if you have the queue daemon running as both does the same?
-
#OpportunisticQM is not needed, but it will perform queue tasks on ordinary requests. When a site works like quitter (polling intervals) it'll just work through the queue faster (assuming there's enough computing powaahrrrr, but the scale we're talking about here isn't a problem for anything anyone uses today). #Cronish functionality is _not_ handled by the daemons, as it will only run onEndActionExecute(...)
-
@mmn So better I enable #Cronish and keep #OpportunisticQM off? Because I like to have lest stuff performed while the regular request (e.g. a user posts a message, clicks a link and such) is done to have good performance.
-
Yeah if you're running daemons you don't _need_ #OpportunisticQM and if running the default interface, you might experience slightly faster page loads that way. Just make sure your daemons are always running. I enjoy using #OpportunisticQM as a backup for crashing daemons. :)
-
@mmn Okay, thank you.