Database - Revision history

Regify: /* Needed Space */

2022-05-06T14:57:51Z

Needed Space

2022-05-06T14:57:30Z

Needed Space

2019-08-19T10:21:15Z

Database Structure

2019-08-19T10:19:14Z

2019-07-26T07:53:39Z

supported database systems

2015-12-07T14:13:28Z

2012-10-30T16:40:22Z

amount of selects, inserts and updates

2010-05-28T09:19:19Z

2010-05-28T09:18:47Z

2009-12-30T14:24:29Z

amount of selects, inserts and updates

← Older revision		Revision as of 14:57, 6 May 2022
Line 16:		Line 16:
	* 600'000 users		* 600'000 users

−	This number increases massively, if you plan to offer ~~'''regichat''' and/or~~ '''regibox'''. Please consider additional 5MB for each regibox user.	+	This number increases massively, if you plan to offer '''regibox'''. Please consider additional 5MB for each regibox user.

← Older revision		Revision as of 14:57, 6 May 2022
Line 16:		Line 16:
	* 600'000 users		* 600'000 users

−	This number increases massively, if you plan to offer '''regichat''' and/or '''regibox'''. Please consider additional 5MB for each regibox ~~user and 2MB for each regichat~~ user.	+	This number increases massively, if you plan to offer '''regichat''' and/or '''regibox'''. Please consider additional 5MB for each regibox user.

@@ Line 4: / Line 4: @@
 == Database Structure ==
-The regify provider database consists of 38 tables, 85 indices (incl. PRIMARY keys, status Dec 2015).
+The regify provider database consists of 49 tables, 95 indices (incl. PRIMARY keys, as of June 2019).
 == Needed Space ==

@@ Line 1: / Line 1: @@
-== supported database systems ==
+== Supported Database Systems ==
 The default database for a regify-provider system is '''MariaDB'''. During installation of the regify software appliance, you are also able to select '''MySQL''' as an alternative.
-== database structure ==
+== Database Structure ==
 The regify provider database consists of 38 tables, 85 indices (incl. PRIMARY keys, status Dec 2015).
-== needed space ==
+== Needed Space ==
-* 1 mio regify transactions need about 185 MB storage capacity.
+* 1 mio regify transactions (regimail, regipay, regibill) need about 185 MB storage capacity.
 * 1000 registered users need about 0,8 MB storage capacity.
@@ Line 16: / Line 16: @@
 * 600'000 users
-This number increases massively, if you plan to offer '''regichat''' and/or '''regibox'''.
+This number increases massively, if you plan to offer '''regichat''' and/or '''regibox'''. Please consider additional 5MB for each regibox user and 2MB for each regichat user.

@@ Line 1: / Line 1: @@
 == supported database systems ==
-The default database for a regify-provider system is '''MySQL'''. During installation of the regify software appliance, you are also able to select '''MariaDB''' as an alternative.
+The default database for a regify-provider system is '''MariaDB'''. During installation of the regify software appliance, you are also able to select '''MySQL''' as an alternative.
 == database structure ==

@@ Line 28: / Line 28: @@
 Database-usage by repeating jobs:
-* mailjob (every 5 minutes)
+* daily job
 ** 1 select per user
 ** 2 inserts per user
@@ Line 37: / Line 34: @@
 ** 0,2 deletes per user
-The conrete values are depending on the number of failed invitings, non collected transactions and other circumstances.
+The conrete values are depending on the number of failed invitings, non collected transactions and other circumstances like average user activity.
 == configuration details ==

@@ Line 46: / Line 46: @@
 === Oracle ===
 The needed charset for Oracle database usage is
 NLS_CHARACTERSET: AL32UTF8
 To allow lot's of users, please check the PROCESSES setting of your Orac le installation. In case this value is less than 200, please rise to a value of 300 to 1000 processes using
 ALTER SYSTEM SET PROCESSES=300 SCOPE=SPFILE;

← Older revision		Revision as of 14:24, 30 December 2009
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.