Enabling and Using Memory Acceleration

• Click Create GeminiDB Instance and perform 5.
• Click Use Existing GeminiDB Instance and select an existing GeminiDB Redis instance.

  Use Existing GeminiDB Instance is only available for primary/standby instances.

1. Enter a rule name.
   Rule Name: Enter a mapping rule name. The rule name must be unique within a GeminiDB instance and cannot exceed 256 characters or include number signs (#).

   Figure 2 Rule name
   
2. Configure source instance information.
   • Database Name: Select a database of the acceleration instance.
   • Table Name: Select a table of the acceleration instance.
   Figure 3 Configuring source instance information
   
3. Configure acceleration instance information.
   • Redis Key Prefix: This parameter is optional. The default value is in the format of Database name:Table name:Field name 1:Field name 2... and can contain a maximum of 1,024 characters. If you have created a custom prefix, it will be used instead of the default one.
   • Value Storage Type: Data type of the cache. Currently, only hash data is supported.
   • Database No. (0-999): ID of a database that stores cached data in the acceleration instance. The default value is 0.
   • TTL (s) Default value: 30 days: Validity period of cached data in the acceleration instance. The default value is 30 days (2,592,000 seconds). If you enter -1, the cached data will never expire.
   • Key Delimiter: Separator among the Redis key prefix, key, and key fields. It is a single character in length.
   Figure 4 Configuring acceleration instance information
   

4. Click Set Key, select a key field of the acceleration instance, and click OK.
   

   If an acceleration instance key consists of multiple source instance fields, the key must be unique in a TaurusDB instance. You can click Up or Down to adjust the sequence of each field.

   Figure 5 Key settings
   

   After the parameters are set, the key is displayed.

   Figure 6 Key
   
5. Configure the acceleration instance fields.
   Move the required fields in the source instance to the acceleration instance.

   Figure 7 Configuring acceleration instance fields
   
6. After setting the parameters, click Submit.

mysql> CREATE DATABASE db1;
Query OK, 1 row affected (0.00 sec)

mysql> CREATE TABLE db1.students(
       sid INT UNSIGNED PRIMARY KEY AUTO_INCREMENT NOT NULL,
       sname VARCHAR(20),
       sclass INT,
       sgender VARCHAR(10),
       sbirthday DATE
       );
Query OK, 0 rows affected (0.00 sec)

mysql> DESC db1.students;
+-----------+--------------+------+-----+---------+----------------+
| Field     | Type         | Null | Key | Default | Extra          |
+-----------+--------------+------+-----+---------+----------------+
| sid       | int unsigned | NO   | PRI | NULL    | auto_increment |
| sname     | varchar(20)  | YES  |     | NULL    |                |
| sclass    | int          | YES  |     | NULL    |                |
| sgender   | varchar(10)  | YES  |     | NULL    |                |
| sbirthday | date         | YES  |     | NULL    |                |
+-----------+--------------+------+-----+---------+----------------+
5 rows in set (0.00 sec)

mysql> INSERT INTO db1.students (sname, sclass, sgender, sbirthday) VALUES ('zhangsan', 1, 'male', '2015-05-20');
Query OK, 1 row affected (0.01 sec)

mysql> SELECT * FROM db1.students;
+-----+----------+--------+---------+------------+
| sid | sname    | sclass | sgender | sbirthday  |
+-----+----------+--------+---------+------------+
|   1 | zhangsan |      1 | male    | 2015-05-20 |
+-----+----------+--------+---------+------------+
1 row in set (0.00 sec)

127.0.0.1:6379> KEYS *
1) "db1:students:sid:1"

127.0.0.1:6379> HGETALL db1:students:sid:1
1) "sbirthday"
2) "2015-05-20"
3) "sclass"
4) "1"
5) "sgender"
6) "male"
7) "sname"
8) "zhangsan"

mysql> INSERT INTO db1.students (sname, sclass, sgender, sbirthday) VALUES ('lisi', 10, 'male', '2015-05-22');
Query OK, 1 row affected (0.00 sec)

mysql> SELECT * FROM db1.students;
+-----+----------+--------+---------+------------+
| sid | sname    | sclass | sgender | sbirthday  |
+-----+----------+--------+---------+------------+
|   1 | zhangsan |      1 | male    | 2015-05-20 |
|   2 | lisi     |     10 | male    | 2015-05-22 |
+-----+----------+--------+---------+------------+
2 rows in set (0.00 sec)

127.0.0.1:6379> KEYS *
1) "db1:students:sid:1"
2) "db1:students:sid:2"

127.0.0.1:6379> HGETALL db1:students:sid:2
1) "sbirthday"
2) "2015-05-22"
3) "sclass"
4) "10"
5) "sgender"
6) "male"
7) "sname"

mysql> UPDATE db1.students SET sclass=12, sname='wangwu' WHERE sid = 1;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0

mysql> SELECT * FROM db1.students;
+-----+--------+--------+---------+------------+
| sid | sname  | sclass | sgender | sbirthday  |
+-----+--------+--------+---------+------------+
|   1 | wangwu |     12 | male    | 2015-05-20 |
|   2 | lisi   |     10 | male    | 2015-05-22 |
+-----+--------+--------+---------+------------+
2 rows in set (0.00 sec)

127.0.0.1:6379> KEYS *
1) "db1:students:sid:1"
2) "db1:students:sid:2"

127.0.0.1:6379> HGETALL db1:students:sid:1
1) "sbirthday"
2) "2015-05-20"
3) "sclass"
4) "12"
5) "sgender"
6) "male"
7) "sname"
8) "wangwu"

mysql> DELETE FROM db1.students WHERE sid = 1;
Query OK, 1 row affected (0.00 sec)

mysql> SELECT * FROM db1.students;
+-----+-------+--------+---------+------------+
| sid | sname | sclass | sgender | sbirthday  |
+-----+-------+--------+---------+------------+
|   2 | lisi  |     10 | male    | 2015-05-22 |
+-----+-------+--------+---------+------------+
1 row in set (0.00 sec)

127.0.0.1:6379> KEYS *
1) "db1:students:sid:2"