Difference between revisions of "Database"
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
== amount of selects, inserts and updates == | == amount of selects, inserts and updates == | ||
| + | |||
| + | Average portal visit: | ||
| + | * 19 selects | ||
| + | * 5 inserts | ||
| + | |||
| + | Sending and receiving one transaction: | ||
| + | * 13 selects | ||
| + | * 4 updates | ||
| + | * 4 inserts | ||
| + | |||
| + | Database-usage by repeating jobs: | ||
| + | * mailjob (every 5 minutes) | ||
| + | ** 1 select | ||
| + | ** 1 delete (only 1 delete per job. More traffic, if sending failed) | ||
| + | * daily | ||
| + | ** 1 select per user | ||
| + | ** 2 inserts per user | ||
| + | ** 0,5 updates per user | ||
| + | ** 0,2 deletes per user | ||
| + | |||
| + | The conrete values are depending on the number of failed invitings, non collected transactions and other circumstances. | ||
Revision as of 16:24, 30 December 2009
Contents
supported database systems
The default database for a regify-provider system is MySQL in version 5.1 or greater. Alternatively, you can use IBM-DB2 database to run the regify-provider.
database structure
The regify provider database consists of 14 tables, 30 indices. There are no stored procedures or views involved.
needed space
- 1 mio regify transactions need about 220 MB storage capacity.
- 1000 registered users need about 0,8 MB storage capacity.
As of theese small values, a capacity of 20GB will fit for about
- 90 mio transactions
- 600'000 users
amount of selects, inserts and updates
Average portal visit:
- 19 selects
- 5 inserts
Sending and receiving one transaction:
- 13 selects
- 4 updates
- 4 inserts
Database-usage by repeating jobs:
- mailjob (every 5 minutes)
- 1 select
- 1 delete (only 1 delete per job. More traffic, if sending failed)
- daily
- 1 select per user
- 2 inserts per user
- 0,5 updates per user
- 0,2 deletes per user
The conrete values are depending on the number of failed invitings, non collected transactions and other circumstances.
