Help Center/
GaussDB/
Best Practices/
Best Practices for Table Design/
Best Practices for Table Design (Distributed Instances)/
Architecture Principles
Updated on 2025-09-04 GMT+08:00
Architecture Principles
Core Principles
- Data type optimization: Integer > Floating-point number > Numeric (in order of priority).
- Index balancing mechanism: trade-off between query acceleration and update costs.
- Partition storage policy: logically unified + physically dispersed.
- Storage engine features: Ustore supports in-place update, and Astore supports append-only.
Solution Advantages
- Improved query performance: Index design and partitioning policies help reduce the scanned data size.
- Reduced storage costs: Selecting appropriate data types can save more than 30% of space.
- Enhanced maintenance efficiency: Independent partition maintenance minimizes impact on services.
- Enhanced concurrent processing: Concurrent access to multiple partitions improves the service throughput.
Parent topic: Best Practices for Table Design (Distributed Instances)
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot