diff options
author | Vladislav Vaintroub <wlad@mariadb.com> | 2020-06-26 14:43:56 +0200 |
---|---|---|
committer | Vladislav Vaintroub <wlad@mariadb.com> | 2020-06-26 14:44:36 +0200 |
commit | d15c839c0dab4016eb425fdb109a5dd8ecd918a4 (patch) | |
tree | 0a7c99f2ccc4f15d2da1dbb00caad4063ad40e2d /sql-bench/as3ap.sh | |
parent | b3acad4a488c51d72ac63c8a686e496975b10479 (diff) | |
download | mariadb-git-d15c839c0dab4016eb425fdb109a5dd8ecd918a4.tar.gz |
MDEV-22990 Threadpool : Optimize network/named pipe IO for Windows
This patch reduces the overhead of system calls prior to a query, for
threadpool. Previously, 3 system calls were done
1. WSARecv() to get notification of input data from client, asynchronous
equivalent of select() in one-thread-per-connection
2. recv(4 bytes) - reading packet header length
3. recv(packet payload)
Now there will be usually, just WSARecv(), which pre-reads user data into
a buffer, so we spared 2 syscalls
Profiler shows the most expensive call WSARecv(16%CPU) becomes 4% CPU,
after the patch, benchmark results (network heavy ones like point-select)
improve by ~20%
The buffer management was rather carefully done to keep
buffers together, as Windows would keeps the pages pinned
in memory for the duration of async calls.
At most 1MB memory is used for the buffers, and overhead per-connection is
only 256 bytes, which should cover most of the uses.
SSL does not yet use the optmization, so far it does not properly use
VIO for reads and writes. Neither one-thread-per-connection would get any
benefit, but that should be fine, it is not even default on Windows.
Diffstat (limited to 'sql-bench/as3ap.sh')
0 files changed, 0 insertions, 0 deletions