Storage analyzer: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 55: Line 55:
<syntaxhighlight lang="text">
<syntaxhighlight lang="text">
     ======= Nonempty Tables =======
     ======= Nonempty Tables =======
       
campaign: 2722 rows, 43 cols, 1038K
        campaign: 2722 rows, 43 cols, 390 By/row, 1038K (+indexes ~331K)
column xx_desctriptionofexposures = 277K
              column xx_desctriptionofexposures = 277K
Empty columns:  entityimageid stageid emailaddress entityimage promotioncodename processid pricelistidTarget pricelistid
              Empty columns:  entityimageid stageid emailaddress entityimage promotioncodename processid pricelistidTarget pricelistid
email: 3 rows, 16 cols, 2K
        email: 3 rows, 16 cols, 679 By/row, 2K (+indexes ~1K)
Empty columns:  actualdurationminutes scheduledend scheduledstart
              Empty columns:  actualdurationminutes scheduledend scheduledstart
resco_mobilereport: 3 rows, 11 cols, 59K
        resco_mobilereport: 3 rows, 11 cols, 20126 By/row, 59K (+indexes ~1K)
resco_question: 4741142 rows, 38 cols, 1614703K -> !!
        resco_question: 4741142 rows, 38 cols, 348 By/row, 1614703K (+indexes ~443K) -> !!
Empty columns:  resco_icon resco_answerstorage resco_defaultvalue
              Empty columns:  resco_icon resco_answerstorage resco_defaultvalue
resco_questiongroup: 1185001 rows, 21 cols, 1463507K -> !!
        resco_questiongroup: 1185001 rows, 21 cols, 1264 By/row, 1463507K (+indexes ~382K) -> !!
column resco_rules = 1223101K
              column resco_rules = 1223101K
Empty columns:  resco_description
              Empty columns:  resco_description
 
Total size of data stored in DB = 986M
Note:
              DB overhead adds ~40%.
              The rest are table indexes - often >50%.
              (Internal tables use to take negligible space.)


     ======= Empty synced entities =======
     ======= Empty synced entities =======


campaignitem
        campaignitem
contract
        contract
contractdetail
        contractdetail
discount
        discount
discounttype
        discounttype
incident
        incident
invoice
        invoice
       
(By removing these entities from customization you could save … API call(s) in each sync) -> !!
        (By removing these entities from customization you could save … API call(s) in each sync) -> !!
 
</syntaxhighlight>
</syntaxhighlight>


In the example above, the campaign entity has 2722 records, 43 columns, and the total size of the stored data is 1038K. Note that the real data consumption is higher because of the database overhead and also because the space occupied by table indexes is not counted.
In the example above, the campaign entity has 2722 records, 43 columns, and the table record stores on average 390 data bytes. The total size of the data stored in the campaign table is 1038K. Table indexes take up an estimated 331K.


The size occupied by individual table columns is listed only in specific cases:
The size occupied by individual table columns is listed only in specific cases:
Line 89: Line 94:


Empty tables (tables containing 0 records) are reported together.
Empty tables (tables containing 0 records) are reported together.
The report shows the net size of the data stored in the database, which is often less than ½ of the size of the database file. This is because the database has substantial overhead and also because of indexes that serve for fast data access.


=== Tips to consider ===
=== Tips to consider ===

Navigation menu