forked from docs/doc-exports
Lu, Huayi
c5fcb46315
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Lu, Huayi <luhuayi@huawei.com> Co-committed-by: Lu, Huayi <luhuayi@huawei.com>
13 lines
1.2 KiB
HTML
13 lines
1.2 KiB
HTML
<a name="EN-US_TOPIC_0000001146786558"></a><a name="EN-US_TOPIC_0000001146786558"></a>
|
|
|
|
<h1 class="topictitle1">How Is the Disk Space or Capacity of GaussDB(DWS) Calculated?</h1>
|
|
<div id="body8662426"><p id="EN-US_TOPIC_0000001146786558__en-us_topic_0000001098976702_p118065892410">A cluster with three data nodes of 320 GB each has a total capacity of 960 GB. When 1 GB data is stored, GaussDB(DWS) stores 1 GB data on two nodes due to duplication, a security mechanism, thereby occupying a total of 2 GB space. As a result, more than 2 GB space is occupied if metadata and indexes are calculated. Therefore, a three-node cluster with a total capacity of 960 GB can store 480 GB data. This mechanism ensures data security.</p>
|
|
<p id="EN-US_TOPIC_0000001146786558__en-us_topic_0000001098976702_p14741155162415">When you create nodes on the console, you are billed by the available capacity of a node. For example, the actual space of <strong id="EN-US_TOPIC_0000001146786558__b1255813285544">dws.m3.xlarge</strong> is 320 GB and the available space displayed is 160 GB, the space you will be billed for.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dws_03_0029.html">Cluster Management</a></div>
|
|
</div>
|
|
</div>
|
|
|