You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This config is undocumented since #758. The default was changed to "yes" and it is quite useless to set it to "no". Yet, it can happen that some user has an old config file where it is explicitly set to "no". The result will be bad performace, since I/O threads will not do all the I/O.
It's indeed confusing.
Either remove the whole option from the code. And thus no need for documentation. OR:
Introduce the option back in the configuration, just as a comment is fine. And showing the default value "yes": # io-threads-do-reads yes with additional text.
If we remove the option completely from the code, valkey refuses to start if the option is present in config. I think it's better to keep it in the code but make it so it has no effect at all.
Since this option is known in Redis still, but you don't want to break backwards compatibility (which I fully understand). After making this option "harmless", I would still only mention the option.. Only mentioning that this option doesn't do anything would be sufficient to remove any confusion by the users.
This config is undocumented since #758. The default was changed to "yes" and it is quite useless to set it to "no". Yet, it can happen that some user has an old config file where it is explicitly set to "no". The result will be bad performace, since I/O threads will not do all the I/O.
It's indeed confusing.
# io-threads-do-reads yes
with additional text.Originally posted by @melroy89 in #1019 (reply in thread)
The text was updated successfully, but these errors were encountered: