Administration Guide : Xinet Statistics and Database Operations — the Database, Admin subtab : Xinet database statistics

Xinet database statistics
The Stats subpanel presents statistics about the database and server. The subpanel is divided into three portions:
Xinet Info
This number shows the number of entries in the user table and reflects the number of different Xinet users who have written information in the database.
This number indicates the number of files which currently have records in the database. Every file in a volume for which the Xinet database has been enabled will have a record. The number of records therefore increases each time a new file is added. Besides files currently online, the number reflects files once-online but now-deleted and files which were once-online but now-archived. Each record indicates the current state of the file. In the case of a file that was moved from online to archive, and then restored, there will be just one record.
This number indicates the number of files that the database registered as archived. When end users browse through a House-style browser, the files will be marked with either red, green or gray triangles.
Red = Files archived to media now offline
Green = Files archived to media now nearline
Gray = Files archived to media and also restored to the file system (both online and archived)
Stored Small Previews
To provide more useful database search results, you can configure Xinet on a per-volume basis to actually store previews in the database. This number shows the number of entries for which thumbnail previews have been stored.
If you are running Video for Xinet with on your server, this shows the number of videos for which keyframes have been rendered and stored.
Xinet users can be put in groups that share volume parameters. This number reflects the number of different Xinet groups who have written information in the database. Refer to Xinet Groups for more information about groups.
This reflects the number of folders which currently have records in the database. The number increases over time, similar to the way the file number increases.
This number reflects the total number of folders that have been archived on the server.
This number shows the number of entries for which larger Web previews have been stored.
This indicates the number of files which have values in any data fields. This applies to XMP as well as any custom data fields.
Server info
This portion presents the same information seen in the Database > Admin > Summary page, as described in Server Info.
Query Cache Info
This section allows you to check on Query Cache operations. Query Cache provides information about turning on the cache and a few tips for evaluating the information that appears here.
Shows whether the Query Cache has been enabled.
Reflects the value set on the Settings page. Xinet recommends that you keep its size at or below 128 Mbytes.
Reflects the total number of queries in the cache.
Shows the number of queries that were returned from the cache.
Shows the total bytes in free blocks
Shows the total number of variable-sized blocks in cache.
Calculated by: Query Cache hits/(Query Cache hits + (Inserts + Not Cached))
Reflects the value established on the Settings page.
Queries that were uncacheable, had a non-deterministic function, or were bigger than the Query Cache Limit.
Records the number of queries that have been stored into the cache.
Number of cached results discarded to make room for new results. Fragmentation can cause this to grow.
Number of blocks of type free. In the worst case you might see (TotalBlocks/2), showing a high degree of fragmentation (a free block followed by a used block followed by a free bloc, etc...). Ideally, you would always have one nice compacted free block, where no space was wasted in between.
Refreshing the Stats page
By default, when you open the Stats page, it will refresh itself every 50 seconds. You may, however, override the default with either the Refresh Now or Stop Refresh buttons. If you click Stop Refresh, contents will remain frozen as long as you view the current page. Clicking Resume Refresh will cause the GUI to revert to its default behavior. Leaving the page and coming back to it later will have the same effect.