Capturing Diagnostic Data

The information on this page is obsolete.  The page is kept for historical reasons but should probably be deleted.

If you experience trouble or poor performance with your SciDB system, SciDB's Resource Monitoring functionality lets you collect system data that helps Paradigm4's Solutions Technicians diagnose and resolve the problems. The diagnostic process includes the following steps:

Enabling Resource Monitoring 

To enable resource monitoring so that SciDB begins gathering data, set the config.ini file's resource-monitoring boolean variable to trueThe default setting is falseWhen resource-monitoring is false, Resource Monitoring is disabled the operators report "Query was executed successfully."  

Specifying How Many Query History Entries to Capture

To specify how many query history entries SciDB captures, set the config.ini file's stats-query-history-size variable to a non-zero value. 

  • The default setting is 32 but consult your Paradigm4 Solutions representative to determine the appropriate value for your system. 
  • If the variable is set to zero, query history is disabled however, SciDB still monitors active queries for their statistics.  If the variable is non-zero, expect some performance impact.  
  • You must restart SciDB for your changes to take effect.

Capturing Data

Once resource monitoring is enabled, run your SciDB system for the length of time, and in accordance with your Paradigm4 Solutions representative's instructions.  

To create the full set of per-instance statistics, run the following query:

$ iquery -aq "stats_instance();"


To create the full set of per-query statistics, run the following query:

$ iquery -aq "stats_query();"

For details on creating individual or statistic subsets see stats_instance() and stats_query().

Send your Data to Paradigm4

After running the query to collecting your data, copy your query results into an email and send them to your Paradigm4 Soultions representative.

Reset Instance Statistics

You can reset your instance statistics at any time by running the stats_instance_reset() operator.