Predict disk space and RAM requirements at configuration time
- Last UpdatedAug 12, 2025
- 4 minute read
The following information describes disk space and RAM usage in various configuration environment scenarios.
Initial Application Installation Data
Disk space and RAM consumption are somewhat predictable for a fresh installation of Microsoft SQL Server, the ArchestrA Bootstrap, the Galaxy Repository, the IDE, and the SMC.
All disk space and RAM capacity in the following table are approximate:
|
Component |
Disk Space |
RAM |
|
Microsoft SQL Server |
55 MB on disk |
22 MB RAM |
|
.NET Framework |
36 MB on disk |
0.6 MB RAM* |
|
AVEVA Bootstrap (including .NET update) |
19 MB on disk |
7 MB RAM |
|
AVEVA Galaxy Repository, IDE, and OCMC |
32 MB on disk |
2 MB RAM |
|
Creating the empty Galaxy and running IDE |
70 MB on disk |
63 MB RAM |
|
Logs for OCMC, starting up OCMC. |
3 MB on disk |
7 MB RAM |
Deployment of the Galaxy's Platform on the Galaxy Repository node, plus the AppEngine object and an Area object, occupies disk space and consumes RAM.
All disk space and RAM capacity values in the following table are approximate:
|
Task |
Disk Space |
RAM |
|
Create GR Platform |
3 MB on disk |
28 MB RAM |
|
Create GR state |
(small increment) |
(small increment) |
|
Create GR first Area |
(small increment) |
(small increment) |
|
Deploy GR Platform |
16 MB on disk |
31 MB RAM |
|
Deploy GR State |
(small increment) |
(small increment) |
|
Deploy GR first Area |
(small increment) |
6 MB RAM |
Creating Simple Object Templates
RAM utilization on the Galaxy Repository node is negligibly affected by the creation of simple object templates. However, certain aggregated, hierarchical Application Objects will immediately consume RAM. Objects that contain multiple child objects (such as the UserDefined Object) consume RAM in the IDE node upon creation of a containing template object.
Creating Derived Templates
Creating individual derived template objects from base template objects has negligible immediate effect upon disk space and RAM consumption. However, large numbers of derived template objects increase the Galaxy Repository size. The database occasionally auto-increments by a 7% to 11% growth factor, as opposed to incrementing when individual objects are created.
You can estimate the expected disk space utilization for each type of derived template object by first determining a size factor for each. Then, multiply the size factor by the planned number of objects of that type. To determine the size factor, create 100 template objects of the particular type and observe the database size impact for the Galaxy Repository.
To analyze the impact of this action, it is not sufficient for you to simply look at the disk size property for the disk drive that contains the Microsoft SQL Server database.
A good approach for determining the incremental size of the Galaxy Repository database is to use Microsoft Query Analyzer and run the sp_spaceused stored procedure against the Galaxy Repository database.
The GR database is visible with the name that you gave the Galaxy when you created it. The sp_spaceused stored procedure returns three columns: database_name, database_size, and unallocated space:
The following table contains an example of calculating the increase in Galaxy Repository database size after creating or importing a specific number of object templates: The size factor for different derived object templates varies due to differing selections of UDA attributes and differing attribute extensions.
|
Galaxy State |
Database Size |
Unallocated Space |
Actual Space Used |
|
Before addition of derived object templates |
11.44 MB |
0.28 MB |
11.14 MB |
|
After addition of 100 derived object templates of type XXX |
12.44 MB |
0.36 MB |
12.08 MB |
|
Database size increase by addition of 100 derived object templates of type XXX |
---- |
---- |
0.94 MB |
|
Calculation of approximate size factor for derived object template of type XXX |
---- |
----- |
0.94 MB/100 = 0.0094 MB |
Derived Object Templates and QuickScripts
If you include a QuickScript as an extension of any derived object template, this will require additional Galaxy Repository database space. The following is an example of a calculation of a size factor for the inclusion of a QuickScript. As the QuickScript in any particular base derived template will be unique, the resulting size factor may need to be calculated for each case.
|
Galaxy State |
Database Size |
Unallocated Space |
Actual Space Used |
|
Before addition of QuickScript |
12.44 MB |
0.36 MB |
12.08 MB |
|
After addition of QuickScript function with 100 lines of code to a derived object template of type XXX |
12.44 MB |
0.36 MB |
12.28 MB |
|
Database size increase for the QuickScript with 100 lines of code |
---- |
---- |
0.20 MB |
Creating Object Instances
Creating instances of base and derived Application Objects (instantiation) has a negligible individual effect on the Galaxy Repository database size. However, large numbers of instances will occupy additional space. To determine the size factors for object instances, use the method described in Deploying Object Instances (following section).
Instances that contain inherited QuickScripts will not use additional disk space in the database; however, the addition of QuickScripts to individual instances of objects will occupy additional disk space.