Analytics & Tracking

Analytics Overview

Frameshift's analytics system continuously collects performance metrics and stores them in a local database, allowing you to track system performance over extended periods and identify trends, bottlenecks, and optimization effectiveness.

Analytics view with historical performance data and statistics

Data Collection

Analytics data is collected automatically in the background without impacting system performance.

Metrics Collected

Frameshift tracks the following metrics every 5 seconds:

Collection Frequency

Data collection adapts based on application focus to minimize resource usage:

• Active window: Metrics collected every 5 seconds at full granularity
• Background window: Collection continues every 5 seconds
• Minimized to tray: Collection continues with reduced frequency

Time Ranges

View your performance data across multiple time ranges to identify short-term issues or long-term trends.

Performance Statistics

For each time range, Frameshift calculates comprehensive statistics to help you understand system behavior.

Available Statistics

Data Visualization

Analytics data is displayed as interactive charts with multiple visualization options.

Chart Types

Data Export PRO

Export your analytics data for external analysis, reporting, or archival purposes.

Export Formats

• CSV (Comma-Separated Values): Compatible with Excel, Google Sheets, and data analysis tools
• JSON (JavaScript Object Notation): Structured data format for programming and automation

How to Export Data

1. Open Analytics Tab

   Navigate to the Analytics section from the main dashboard.

2. Select Time Range

   Choose the time range you want to export (15 minutes to 30 days).

3. Click Export Button

   Click the "Export Data" button in the top-right of the analytics view.

4. Choose Format and Save

   Select CSV or JSON format and choose a save location. The file will include all metrics and timestamps for the selected range.

Database Storage

Analytics data is stored locally on your system using SQLite (compiled to WebAssembly via SQL.js).

Storage Location

The analytics database is located at:

• %APPDATA%\Frameshift\analytics.db

Database Management

• Automatic cleanup: Data older than 30 days is removed daily
• Typical size: 50-100 MB for 30 days of data
• Backup: Database file can be manually copied for backup
• Clear data: Delete database file to start fresh (app will recreate it)

CREATE TABLE metrics (
  id INTEGER PRIMARY KEY AUTOINCREMENT,
  timestamp INTEGER NOT NULL,
  cpu REAL NOT NULL,
  gpu REAL NOT NULL,
  ram REAL NOT NULL,
  vram REAL NOT NULL,
  diskRead REAL,
  diskWrite REAL,
  netUp REAL,
  netDown REAL
);

CREATE INDEX idx_timestamp ON metrics(timestamp);

Using Analytics Effectively

Here are some practical ways to use analytics data to improve your system performance:

Identifying Bottlenecks

• CPU at 100%, GPU low: CPU bottleneck - optimize CPU settings or upgrade processor
• GPU at 100%, CPU low: GPU bottleneck - adjust graphics settings or upgrade GPU
• RAM near 100%: Memory bottleneck - close background apps or add more RAM
• High VRAM usage: Reduce texture quality or graphics settings in games

Measuring Optimization Impact

Follow these steps to quantify the effectiveness of optimizations:

1. Export analytics data for your typical usage (1 day or 7 days)
2. Note the average and 95th percentile values for CPU, GPU, and RAM
3. Apply Frameshift optimizations
4. Use your system normally for the same duration
5. Export analytics data again and compare metrics
6. Look for reductions in average usage and improved 1% low FPS in games

Tracking Long-Term Trends

Use 7-day and 30-day views (Pro) to identify:

• Performance degradation: Gradual increase in baseline CPU/GPU usage may indicate malware or bloatware accumulation
• Temperature trends: Rising temperatures over time may indicate dust buildup or thermal paste degradation
• Usage patterns: Identify peak usage times and optimize your schedule accordingly