Project Size and Growth

The disk space necessary for analyses varies depending on your analysis model as well as the amount of information analysed.

As a result, it is difficult to predict accurately the amount of space that your Squore installation will use. After a few runs, you should be able to estimate disk space requirements by working out the space required to analyse an artefact with your analysis model. Keep in mind that the first version of a project is always more costly than subsequent analyses, and that an analysis with only a few changes will use a lot less space than an analysis where there are a lot of changes.

Here is an example based on the Risk Index model, one of the standard multi-language models shipped in Squore 16.1.

Table 7.1. Project Characteristics

First Code Snapshot

Second Code Snapshot

Language Distribution

C (13%), C++ (14%), Java (73%)

C (9%), C++ (11%), Java (80%)

Source Files

20000

30000

10% of previous code changed

Classes

28000

47000

Methods and Functions

181000

296000

Lines of Code

5.2M

7.6M

Effective Lines of Code

2.6M

3.6M

Findings

157000

234000

Action Items

7700

6300


Table 7.2. Model Characteristics

Average metrics per artefact

160

Average indicators per artefact

15


Table 7.3. Project Cost

Database Growth

Project Folder Growth

V1 (Snapshot 1)

+3.5GB

+839MB

V2 (Snapshot 1)

+100MB

+1MB

V3 (Snapshot 2)

+3GB

+1.1GB