View - Capacity/Billing planning on usage of DASD

### View - Capacity/Billing planning on usage of DASD

book

calendar_today

View

#### Issue/Introduction

I have been asked about a formula in our View extract job that we have been using for years in our Capacity Planning.

We want to incorporate this into the additional tracking processes so we are following the line-of-business utilization for View.

The formulae convert the number of report lines to gigabytes.  The number 1,024,000,000 represents raw Gigabytes, and the number 1,073,741,824 represents what the team uses to calculate Gigabytes.

The question in this case regards the number 330 in the equations. The formulae were written many years ago, and we are not sure where the number came from.

In the View database, the lines are concatenated with the spaces compressed out of the data, so a report line of length 133 takes up less than 133 bytes of space.

Here are the equations:

SPACE_ALLOC_MICS_GB = LINES * 330 / 1024000000

SPACE_ALLOC_GB      = LINES * 330 / 1073741824

Release : 14.0

Component :

#### Resolution

When looking at things strictly from a mathematical perspective, the basic equation would have a structure of:

(# of lines x (# of bytes/(y lines))) / (# bytes in 1 GB) = # of GB for "an entity"

For a standard text report of 133 bytes/line, there would be compression involved in the storage of the report, whereas View tapes and the database disk layer would have different compression ratios.

Depending on settings, compression on tapes would depend on the hardware compression ratios.

In the client's equations, the value of "330" must have been somehow calculated from the "(# of bytes/(y lines))" from above. where the "y" would represent a grouping of multiple report lines.