百度智能云

All Product Document

          Distributed Relational Database Service DRDS

          FAQs About Configuration

          How to select cloud database DRDS specification?

          The processing capability of the DRDS depends on the specifications of single storage node and the number of nodes. Users should configure the read/write performance of middleware proxy and backend nodes in a balanced manner to avoid performance bottleneck. For a detailed description, see How to Select DRDS Configuration.

          How to select the number of DRDS multiparts?

          Multipart is an important strategy for the DRDS to balance service traffic. Each multipart of the DRDS bears part of service traffic. The current DRDS supports 2, 4, 8 and 16 multiparts. Users can select the number of multiparts according to the data volume and business performance requirements:

          • Impact of data volume. The current DRDS supports 64 sub-tables, i.e., the number of tables on each multipart = 64/multipart. The data volume of a single multipart should not exceed 500 G, so the number of multiparts = total data volume/500 G.
          • Impact of business performance requirements. With the equal data volume, the larger the number of multiparts, the smaller the data volume in each multipart, and the higher the performance.

          How to select a DRDS sub-table key?

          One major advantage of the distributed database is to horizontally split the original datasheet into several sub-tables. Thus, it can split and balance business pressure by placing the sub-tables at different backend nodes to improve system efficiency. Therefore, reasonable selection of the sub-table keys is the key factor to properly split the datasheet. Notes for selecting the sub-table keys are as follows:

          • The main body related fields on business logic are selected as the sub-table keys;
          • The sub-table keys should facilitate splitting the original database into several sub-tables with a balanced size;
          • Try to avoid using the hot spot data as the sub table keys.

          Which general SQL syntaxes are not supported by DRDS?

          For general SQL syntaxes currently not supported by DRDS, see Use Limits.

          Previous
          Operation Guide
          Next
          SLA-Service Level Agreement (SLA)