![]() |
Questions about query_read() vs. query_read_slave()
I'm developing a plugin with a lot of SQL reads and I'd like to optimize it as much as possible. One optimization I'd like like to look into is switching all of my query_read functions to query_read_slave functions.
I've read that query_read_slave() should be used when timing is not vital (source).
I've also read that "you only use query_read_slave when you have more than 1 query running together" (source).
If you guys can answer some of these questions, I would be very grateful. :) |
If there is no slave database, there should be no increase or descrease in performance.
Displaying the result of a search is for example not considered critical, reading the permissions of a user in order to determine if the post he is making is allowed might be critical. |
Alrighty. Thanks for clearing that up!
|
All times are GMT. The time now is 07:30 AM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|