4 2.1. Generic response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. SQL response . . . . . . . . 2.3. Fetch response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.4. Slice response . . . . . . deferring the read of the response. Chapter 1. Introduction 3 Chapter 2. Responses The wire protocol has a limited set of responses. Some operations have a specific response, which is described together

MySQL with SSDs Page 7 MySQL Server 95th percentile response times for Config #3 (dual socket) MySQL Server maximum response times for Config #3 (dual socket) In the case of SAS‐HDD 000.00 2,000.00 3,000.00 4,000.00 5,000.00 6,000.00 7,000.00 milliseconds 95th percentile Response Time ‐ New Order 50 c 100 c 150 c sas‐hdd 20,300.16 49,452.06 sata 4,699.63 15,759.15 37,367 78 ‐ 10,000.00 20,000.00 30,000.00 40,000.00 50,000.00 60,000.00 milliseconds Maximum Response Time ‐ New Order Best Practices for MySQL with SSDs Page 8 BKM innodb_adaptive_hash_index

Client ? Request-1 Response-1 Request-2 Response-2 Request-3 Response-3 Request-4 Response-4 Request-1 Request-2 Response-1 Request-3 Response2 Response-3 Request-4 Response-4 RPC-1 RPC-2

bytes response_size The compressed size of the response package being sent back down to the client, in bytes status The HTTP status code of the response • 200 -- successful request, response package package sent back to the client • 204 -- successful request, no response package sent back • 304 -- /pull, but nothing new to send back • 401 -- authentication failed 1Members of zumero_users_admin are also that occurred, in JSON full_request_size Same as request_size, but uncompressed full_response_size Same as response_size, but uncompressed txid_max (internal use) ahttp://en.wikipedia.org/wiki/Unix_time

pushed. You can also choose a branch manually. Addressing Changes If you need to make changes in response to the reviewer’s comments, just make another commit on your branch and then push it again: $ git is ignored. options query.ExecuteOptions ExecuteOptions is passed around for all Execute calls. Response ExecuteBatchKeyspaceIdsResponse is the returned value from ExecuteBatchKeyspaceId. 70 Properties Name Description keyspace_id bytes keyspace_id is the associated keyspace_id for the entity. Response ExecuteEntityIdsResponse is the returned value from ExecuteEntityIds. Properties Name Description

(https://github.com/vitessio/vitess/compare). Addressing Changes If you need to make changes in response to the reviewer’s comments, just make another commit on your branch and then push it again: $ git is ignored. options query.ExecuteOptions ExecuteOptions is passed around for all Execute calls. Response ExecuteBatchKeyspaceIdsResponse is the returned value from ExecuteBatchKeyspaceId. Properties type is NULL_TYPE. keyspace_id bytes keyspace_id is the associated keyspace_id for the entity. Response ExecuteEntityIdsResponse is the returned value from ExecuteEntityIds. Properties Name Description

RegionServer-1 RegionServer-2 scanResultCache ScannerCallableWithReplicas 1. RPC Request 2. RPC Response 3. Regroup and enqueue 4. Return a result Step.1 + Step.2 + Step.3 = loadCache Concepts in Scan Cell-5 Result-4 Cell-7 Result-5 Cell-6 Cell-8 Cell-2 Result-2 Cell-3 RegionServer Row Data RPC Response Recieved from RS Results get from scanner.next() Cell-9 Size of cell-1 > 1MB scan.setCaching(2) Cell-5 Result-4 Cell-7 Result-5 Cell-6 Cell-8 Cell-2 Result-2 Cell-3 RegionServer Row Data RPC Response Recieved from RS Results get from scanner.next() Cell-1 Cell-2 Result-1 Cell-3 Cell-4 Result-2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 18.2. Response Codes Are Usually Zero. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . encountered. Always check the response code returned by gfix to be sure that it worked. However, see the caveats section below for details because it looks like the response code is always zero — at least transaction -object my_employee is in use linux> echo $? 0  As with many failures of gfix, the response code returned to the operating system is zero. Under Firebird 2, the error message is more self-explanatory:

described in The implementation of POSTGRES, was released to a few external users in June 1989. In response to a critique of the first rule system (A commentary on the POSTGRES rules system), the rule system this example named mydb, you use the following command: $ createdb mydb This should produce as response: CREATE DATABASE If so, this step was successful and you can skip over the remainder of this section administrator or check back in the installation instructions to correct the situation. Another response could be this: createdb: could not connect to database template1: could not connect to server:

described in The implementation of POSTGRES, was released to a few external users in June 1989. In response to a critique of the first rule system (A commentary on the POSTGRES rules system), the rule system this example named mydb, you use the following command: $ createdb mydb This should produce as response: CREATE DATABASE If so, this step was successful and you can skip over the remainder of this section administrator or check back in the installa- tion instructions to correct the situation. Another response could be this: createdb: could not connect to database template1: could not connect to server: