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
The point-get query can use max uint64 as tso when only has 1 rpc request.
Similarly, try to use max uint64 as tso for table/index reader which only has 1 cop task, and in autocommit transaction.
Here is an example:
createtablet (id int key, b int, c int, index idx(b));
For the following query, only read a small range of data, and in most cases, there will be only 1 cop RPC request, then we can use max uint64 as tso too, there will be some performance improvements for small queries.
select*from t where id >1and id <10;
Drawback
This change may break linearizability, so this optimization can only be used when the tidb_guarantee_linearizability is disabled.
The text was updated successfully, but these errors were encountered:
Enhancement
The point-get query can use max uint64 as tso when only has 1 rpc request.
Similarly, try to use max uint64 as tso for table/index reader which only has 1 cop task, and in autocommit transaction.
Here is an example:
For the following query, only read a small range of data, and in most cases, there will be only 1 cop RPC request, then we can use max uint64 as tso too, there will be some performance improvements for small queries.
Drawback
This change may break linearizability, so this optimization can only be used when the
tidb_guarantee_linearizability
is disabled.The text was updated successfully, but these errors were encountered: