Data Warehouse
The data pool stores heartbeat data collected by the collection proxy, used by the heartbeat simulation proxy during replacement.
Page Layout
┌───────────────────────────────────────────────────────┐
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ Total │ │ 🌐Global │ │ 👤Account│ │
│ │ 1234 │ │ 800 │ │ 434 │ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ 19-bit │ │ 20-bit │ │ 22-bit │ │
│ │ 500 │ │ 400 │ │ 334 │ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ │
│ [Refresh] [Clear Pool] Game:[ ▼ ] Account:[ ▼ ] │
│ Auto Cleanup: ● Running [Start/Stop] [Settings] ⓘ │
│ Database: [Export Database] [Import Database] ⓘ │
│ │
│ Heartbeat Data Pool 🌐Global 👤Account │
│ ┌────┬──────┬──────┬──────┬────┬────┬────┬────┬───┐ │
│ │ ID │Source│ Type │GameID│Bits│Hdr │Size│Qual│...│ │
│ ├────┼──────┼──────┼──────┼────┼────┼────┼────┼───┤ │
│ │ │ │ │ │ │ │ │ │ │ │
│ └────┴──────┴──────┴──────┴────┴────┴────┴────┴───┘ │
│ │
│ Page 1/10 [First][Prev] [1] [Next][Last] Per page 20│
└───────────────────────────────────────────────────────┘
Data Pool Overview
Six statistics cards are displayed at the top:
| Card | Description |
|---|---|
| Total | Global + Account pool combined (large green number) |
| 🌐 Global Pool | Heartbeat data not associated with a specific account (orange) |
| 👤 Account Pool | Heartbeat data associated with specific SOCKS5 accounts (green) |
| 19-bit ID | Data entries with 19-byte GameID length |
| 20-bit ID | Data entries with 20-byte GameID length |
| 22-bit ID | Data entries with 22-byte GameID length |
ID length statistics help assess the distribution of different game types in the data pool.
Viewing and Filtering Data
Filter Dimensions
- Game Type: Dropdown to filter by game type identified during collection
- Account: Dropdown to select [All] / [Global Pool] / specific SOCKS5 account
Data Grid
Each record displays the following columns:
| Column | Description |
|---|---|
| ID | Sequence number |
| Source | 🌐 Global Pool / 👤 Account Pool |
| Game Type | Game type identified during collection |
| GameID | Player identifier |
| Bits | GameID byte length |
| Header | Packet header bytes |
| Size | Packet size |
| Quality | Quality score |
| Usage Count | Times used for heartbeat replacement |
| Collection Time | Data storage time |
| Data Preview | Hex preview of raw data |
Pagination
Page controls at the bottom:
- First / Previous / Next / Last navigation buttons
- Page Input: Jump directly to a specific page
- Per Page: Customize items per page
Auto Management
Auto management periodically cleans the data pool to maintain a reasonable size.
Controls
- Start/Stop: Control the auto cleanup service
- Settings: Open auto management configuration
Settings
| Setting | Default | Description |
|---|---|---|
| Cleanup Interval | — | Auto cleanup interval (minutes) |
| Max Pool Size | — | Threshold to trigger cleanup |
| Target Pool Size | — | Target size after cleanup |
| Auto Start | No | Start auto management on app launch |
Cleanup Strategy
Auto management prioritizes removing:
- Most frequently used data (heavily reused data has less value)
- Oldest collected data
- Lower quality score data
Database Operations
Refresh
Reload current page data to reflect the latest pool state.
Clear Data Pool
Delete all collected heartbeat data.
This operation is irreversible. All heartbeat data will be permanently deleted.
Export Database
Backup the SQLite database file to a specified location, including all configuration and heartbeat data.
Import Database
Restore database from a backup file.
Import overwrites all current data and configuration. Export a backup first.