Synology Cloud Station Performance


Performance Benchmark

Synology Cloud Station the here we describe the performance of the Cloud Station that runs on several NAS Synology models, hoping to explain the capabilities and limits of their use in the real world. Note that the switch is 1 Gbps, and no other service is activated on the NAS server during reference testing. See See Testing Environment for more. Indexing Performance and Measurement of Cloud Database Indication Database.

Indexing is needed for the Cloud Station to calculate the hashes and each file and write them into the database, which allows the Cloud Station server to restore files. As intended by the graph, the time needed to process one file increases as the basic measure of data grows in general. This means indexing performance is inversely proportional to the database size, and the lower end product, the steeper the climb (the stronger the impact).

This result is from the SQLite engine database - the basic data backend provided by Cloud Station. SQLite machines use one on-disk file as a database to store tables, records, and indexes. Inserting new records in such files requires an index to be updated, and very often in a random position, which means that almost every page in the index must be updated.

Test Results

This brings our attention to two things. CPU and I or O server, the speed that determines the efficiency of index updates and the number of records in the database, which determines the size of the index. The larger the index, the longer it takes to renew and thus the more time it takes to respond. When designing a database, you may have to estimate how large the database will be when it is filled with data. Estimating the size of the database can help determine the hardware configuration needed to do the following.

Achieve the performance needed by the application. Make sure the amount of physical disk space needed to store data and indexes. Estimating database size can also help determine whether the database design needs to be refined. For example, you can determine that the estimated database size is too large to apply to the organization and more normalization is needed. The estimated size may be smaller than expected. This will make it possible to normalize the database to improve query performance.

The approximate size can estimate the size of the database, estimate the size of each table individually and then add the value obtained. The size of the table depends on whether the table has an index and, if they do, what type of index. Here we can estimate the amount of space needed to store data in a table. Calculate the space needed for the stack or clustered index following the instructions in Estimating Heap Size or Estimating the Size of a Clustered Index. For each index not included, calculate the space needed.

Discussion: