-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enable low-level optimization #23
enable low-level optimization #23
Conversation
@@ -24,6 +24,8 @@ import net.spy.memcached.ops.OperationQueueFactory | |||
* @param operationTimeout is the default operation timeout; When the limit is reached, the | |||
* Future responses finish with Failure(TimeoutException) | |||
* | |||
* @param shouldOptimize If true, low-level optimization is in effect. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Took me a while to track down exactly what happens if this is true, but it seems at the end of the day this option gets propagated to the MemcachedConnection
, where, the effect is:
If true, optimisation will collapse multiple sequential get ops.
Can you please add that that description into the parameter ScalaDoc ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dit it.
How does that look?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great LGTM.
enable low-level optimization
👍 but guys, what's the default in SpyMemcached? Assuming no downsides, wouldn't it be more beneficial to default to true? |
@alexandru: Both In the interests of safety I think we should keep it as |
OK, then |
enable low-level optimization
enable low-level optimization
I'd like to use
ConnectionFactory.shouldOptimize()
.