Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/sql/docs/postgres/choosing-ssd-hdd below:

Choose between SSD and HDD storage | Cloud SQL for PostgreSQL

Stay organized with collections Save and categorize content based on your preferences.

When you create a Cloud SQL instance, you choose whether it stores data on solid-state drives (SSD) or hard disk drives (HDD):

• SSD storage is the most efficient and cost-effective choice for most use cases.
• HDD storage is sometimes appropriate for large datasets (>10 TB) that are not latency-sensitive or are infrequently accessed.

Regardless of which type of storage you choose, your data is stored on a distributed, replicated file system that spans across many physical drives.

The guidelines on this page can help you choose between SSD and HDD.

There are several reasons why it's best to use SSD storage for your Cloud SQL instance:

• SSD is faster and has more predictable performance than HDD.
• HDD throughput is much more limited than SSD throughput.
• Individual row reads on HDD are slow. Because of disk seek time, HDD storage supports only 5% of the read rows per second of SSD storage. Large multi-row scans, however, are not as adversely impacted.
• The cost savings from HDD are minimal, unless you're storing large amounts of data. Consider using HDD storage if you're storing at least 10 TB of data.

HDD storage is suitable for use cases that meet the following criteria:

• You expect to store at least 10 TB of data.
• You do not use the data to back a user-facing or latency-sensitive application.

• Your workload falls into one of the following categories:

  • Batch workloads with scans and writes, and no more than occasional random reads of a few rows.
  • Data archival, where you write large amounts of data and rarely read that data.

For example, if you plan to store extensive historical data for a large number of remote-sensing devices and then use the data to generate daily reports, the cost savings for HDD storage might justify the performance tradeoff. On the other hand, if you plan to use the data to display a real-time dashboard, it probably would not make sense to use HDD storage—reads would be much more frequent in this case, and reads are much slower with HDD storage.

When you create a Cloud SQL instance, your choice of SSD or HDD storage for the instance is permanent.

If you need to convert an existing HDD instance to SSD, or conversely, you can export the data from the existing instance and import the data into a new instance. Keep in mind that migrating an entire instance takes time.

Create an instance with SSD or HDD storage.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-14 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4