Settings · System
The status of the database, table sizes, backups and data fetch logs.
Database
What it is: Database type, connection or file, size, the kind of sector factor and the primary data source; a backup button.
What data feeds it: /api/system/database and /api/system/status. The development profile uses an SQLite file, the production profile PostgreSQL.
What it shows: For SQLite, the file path, size and journal mode; for PostgreSQL, the connection address. The backup button works with VACUUM INTO on SQLite; on PostgreSQL it says that pg_dump should be used.
What can be concluded from it: If the sector factor is "DERIVED", the sector indices could not be obtained from the source and were derived from the average of the sector's members. As the database grows, old backtest signals are deleted automatically; live records are not touched.
Tables
What it is: The row counts of all the application's tables.
What data feeds it: A COUNT(*) query for each table.
What it shows: The size of the symbol, price_daily, return_daily, event, analysis_run, pipeline_run, analysis_result, signal_daily, signal_outcome and fetch_log tables.
What can be concluded from it: It is normal for signal_daily to have millions of rows: a single walk-forward run writes about 2.4 million signals. price_daily being smaller than expected shows that data fetching was left incomplete.
Data fetch logs
What it is: The time, symbol, source, row count, status and message of the last 300 data fetch requests.
What data feeds it: The fetch_log table; after each data fetch request, a row is added with the source's name, the requested date range, the number of rows written and the error message, if any.
What it shows: Which range was fetched from which source, and the error message of failed requests.
What can be concluded from it: Repeated errors on the same symbol show that the source does not recognise that symbol, while errors seen on all symbols at once point to an outage in the network or the source; in the latter case it is enough to repeat the fetch later.
The investment information, comments and recommendations given here are not within the scope of investment advisory services. Investment advisory services are provided under an investment advisory agreement to be signed between a client and brokerage houses, portfolio management companies, or banks that do not accept deposits. The signals here are produced from historical data with statistical models, are shown the same to everyone and are not personalised; they may not suit your financial situation or your risk and return preferences. Therefore, making investment decisions based solely on the information given here may not produce results that meet your expectations.