Profiling by Cube
Through the profiler service, information generated by each cube published in O3 Server is stored in files like the one described below.
Each cube generates one separate file.
Generation: one record is created each time a query is performed on a cube.
Field Name |
Type |
Description |
---|---|---|
Date |
dd/mm/yyyy |
Date of the query |
Hour |
hh:mm:ss |
Time of the query |
Precalc |
String |
It states if any redundancy level has been calculated. Its values can be: True or False |
query_level |
String |
Level the query was made at |
View |
String |
If the user has accessed the cube through a view, it states the name of such view |
User |
String |
User who made the query |
Role |
String |
Role through which the user who has made the query accessed the cube |
Ip |
String |
IP Address from which the user who has made the query is accessing the cube |
query_time |
Integer |
Query time in milliseconds |
distance |
Integer |
Distance between query level and precalc as vectors difference |
blocks_accesed |
Integer |
Total number of blocks accessed to solve the query |
blocks_fault |
Integer |
Total number of blocks that were not found in the cache and were necessary to solve the query |
used_cube_cache |
Integer |
Size of the cache used by the cube at the time of the query measured in blocks |