We ran DBT-1 while PITR is configured on PostgreSQL8.1.4. After running DBT-1, we evaluated the offline backup, the base restoration and PITR performance using the tar czf command.
| H/W | HITACHI HA8000/110W HB |
|---|---|
| CPU | Intel Xeon HT OFF |
| 2GB | |
| HDD | 220GB |
| OS | RHEL4 2.6.9-11.Elsmp |
| PostgreSQL 8.1.4 | |
| OSDL DBT-1 2.1 |

Figure 1: Disk Layout
How these hard disks are used is shown in Table 2.
| Device Name | Use | Mouse Point |
| /dev/sda | For storing the OS and execution log | / |
| /dev/sdb | For executing DBT-1 and storing the backup target DB | /data |
| /dev/sdc | For storing backup files and WAL | /data2 |
We loaded an approximately 7GB table generated using "./datagen -d PGSQL -i 10000 -u 1000" and an approximately 53GB table generated using "./datagen -d PGSQL -i 10000 -u 8000" into PostgreSQL and ran DBT-1 for 3 hours, 7 hours and 10 hours. The performance was measured while increasing the invalid area in the data cluster.
Measurement procedure manual
Figure 2 shows the backup time for each backup start time of the 7GB table.
Figure 2 Backup Time for Each Backup Start Time of the 7GB Table
Figure 3 Backup Time for Each Backup Start Time of the 53GB Table
Figure 4 Backup File Size for Each Backup Start Time of the 7GB Table
Figure 5 Backup File Size for Each Backup Start Time of the 53GB Table
Figure 6 Base Restoration Time for Each Backup Start Time of the 7GB Table
Figure 7 Base Restoration Time for Each Backup Start Time of the 53GB Table
Figure 8 WAL Size for Each DBT-1 Execution Time of the 7GB Table
Figure 9 WAL Size for Each DBT-1 Execution Time of the 53GB Table
Figure 10 CPU Activity Ratio During the Backup/Restoration Process while Running DBT-1 Using the 7GB Table
Figure 11 CPU Activity Ratio During the Backup/Restoration Process while Running DBT-1 Using the 53GB Table
Figure 12 Disk I/O During the Backup/Restoration Process while Running DBT-1 Using the 7GB Table
Figure 13 Disk I/O During the Backup/Restoration Process while Running DBT-1 Using the 53GB Table