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
Add socket protocol support and trim the encode path
The shackle protocol is now configurable with the protocol app env,
so pools can run on shackle_socket instead of gen_tcp. The setup
path (startup, auth, use keyspace) picks gen_tcp or the socket
module based on the socket type.
encode_long_string no longer copies the query into a fresh binary,
and the query flags are computed with direct map lookups instead of
four query_opts round trips.
Against a local Scylla (64 callers, pool of 16), shackle_socket cuts
client CPU from ~24.8 to ~19.8 us per request; throughput is server
bound and unchanged. Requires a shackle release with shackle_socket
when the protocol env is set; the default is unchanged.
0 commit comments