How long will UUID migration take?


  • 50k Excellentable migration on MS-SQL and Oracle database will need available memory space of 20G.

  • The estimate applies to following version upgrade paths:

    • 4.1.x → 4.2.1.x → 4.2.3

    • 4.1.x → 4.2.3

  • The time values mentioned below are an estimated value and are subjected to change based on resource allocation and availability at the customer end.


Specification

No. of Users

No. of Excellentables

Postgres

(Time in sec)

MySQL

(Time in sec)

MS-SQL

(Time in sec)

Oracle 

(Time in sec)

DC

(Time is sec)



JVM: 8G




20

1K

35

27

45

 42

49

100

5K

139

110

207

186

204

200

10K

264

240

432

381

416

500

25K

712

974.5

1012

995.5

1152

1000

50k

1353 

3321

1320 (MS-SQL Standard edition)

2047

2389



The charts below show the time comparison for performing the following actions before and during the migration when upgrading to 4.2.3 

  • Creating a page

  • Opening the page in view mode



Specification


Actions

Baseline Time - Pre-Migration  (in secs)

During Migration (in secs) 

Postgres

MySQL

MS-SQL

Oracle

DC

Postgres

MySQL

MS-SQL

Oracle

DC


JVM: 8G  

No of Excellentables: 10k



Creating a page


22


23


21


17


21


39


30


43


25


22


Opening the page in view mode


5


3


2


3


3


3


3


11 


3


4

JVM: 8G   

No of Excellentables: 25K


Creating a page


23 


25 


21 


18 


20 


30


32


42


35


30


Opening the page in view mode


4


4


2


2


3


4


4


3


3


3

JVM: 8G   

No of Excellentables: 50K


Creating a page


25


20


17


18


20


37


30


33


33


22


Opening the page in view mode


4


3


2


2


3


4


4


3


4


4




 For the version upgrade path 4.1.x → 4.2.1 → 4.2.1.x →4.2.3, please consider below estimate for migration of 50k Excellentables



No of users


No of Excellentables

Migration Time (in secs)

Postgres

MySQL

MS-SQL

Oracle

DC

1000

50k

2102

5406

1020

2803

6800