Most traders who download DennTech's free desktop utilities use perhaps thirty percent of their total capability. The Windows Cleaner and System Monitor ship with sensible defaults optimized for immediate value — but within their configuration layers lie features specifically designed for the demands of 24/7 automated bot operation that most casual users never discover. This guide is written for bot traders who are already running the DennTech desktop bot and want to extract the maximum system reliability benefit from the free tools their bot subscription includes access to. Every feature documented here is available at no additional cost from the free apps page.
The System Monitor: Beyond the Dashboard Glance
The System Monitor's primary interface — the real-time dashboard showing CPU load, RAM utilization, disk I/O, and network throughput — is useful for a quick health check. The power users, however, are operating in the Monitor's alert configuration and logging subsystems, which transform it from a passive display into an active guardian of bot uptime.
Configuring Threshold Alerts
The System Monitor supports configurable alerts on all primary metrics. For bot traders, the critical thresholds to configure are:
- CPU usage > 85% sustained for 60 seconds: Indicates the bot process or a background Windows service is consuming excessive resources, potentially degrading order execution speed. The alert triggers a system notification and logs the event with a process identifier for diagnosis.
- Available RAM < 400MB: When available RAM drops below this threshold, Windows begins using the page file (virtual memory on disk), causing latency spikes that can affect order execution timing. Bot traders running multiple strategy instances simultaneously should set this threshold conservatively. Review the getting started guide for recommended minimum system specifications.
- Network latency > 150ms (sustained): Elevated latency degrades WebSocket connection quality to the exchange API. The System Monitor can ping the exchange API endpoints at configurable intervals and alert when round-trip time exceeds the configured threshold, allowing you to investigate your connection quality before it causes missed orders.
- Disk free space < 2GB: The DennTech bot writes trade logs and performance data continuously. Running out of disk space causes the bot to stop logging, and in edge cases can corrupt the SQLite queue database used for order delivery assurance. This alert is a simple preventive measure.
Configure these thresholds in the System Monitor's Settings panel under "Alert Configuration." Each alert type can be directed to a Windows notification, a log entry, or both. For traders who leave the bot running unattended, log-based alerts that survive session changes are more reliable than notification-only alerts.
The Performance Timeline Log
The System Monitor's Performance Timeline feature — disabled by default to minimize disk I/O — records a rolling 30-day history of system metrics at 5-minute intervals. Enabling this feature requires approximately 45MB of disk space per month and provides enormous diagnostic value. When your bot underperforms during a specific time window, the performance timeline lets you correlate the trading period with system resource consumption data. Discovering that the bot's execution latency spiked on Tuesday morning because a scheduled Windows Update ran at 3am — consuming CPU and causing API reconnections — is only possible with historical performance data. Enable the timeline in the System Monitor's "Data Collection" tab.
Startup Sequence Management
A frequently overlooked System Monitor capability is startup sequence management. When your bot machine boots (after a power outage, update restart, or system reset), the order in which processes start matters. The DennTech bot must connect to the exchange API before it can execute any orders, but the exchange WebSocket connection is fastest when network interfaces are fully initialized. The System Monitor's startup watchdog verifies that the bot process has launched and established an exchange connection within a configurable time window after system boot, sending an alert if it has not. This replaces the need to manually verify bot operation after every system restart.
The Windows Cleaner: Precision Maintenance for Bot Systems
General-purpose Windows cleaners are designed for desktop consumer use cases: clearing browser caches, removing temporary files, and cleaning registry entries. The DennTech Windows Cleaner extends this baseline with maintenance routines specifically targeted at the files and processes that accumulate during extended bot operation.
Bot Log Rotation Cleanup
The DennTech bot generates trade logs, error logs, and strategy state files continuously. Over weeks and months of operation, these files accumulate significantly. The Windows Cleaner's Bot Log Maintenance module identifies DennTech-specific log files that exceed a configurable age and size threshold and archives or removes them according to your retention policy. Critically, it differentiates between logs still needed for open-position auditing (preserved regardless of age) and fully settled historical logs (eligible for cleanup). This prevents the silent disk-space exhaustion that has caused more than a few traders' bots to stop logging mid-trade.
Scheduled Maintenance Windows
The Windows Cleaner supports scheduled maintenance windows — automated cleanups that run at configurable times, typically during low-activity market hours (3am-5am UTC on weekdays). A properly configured maintenance window performs: temp file cleanup, browser cache flush, Windows Update staging folder cleanup, and prefetch file optimization. The combined effect is that the bot machine stays lean and the bot process runs in a consistently clean resource environment rather than gradually degrading performance as disk fragmentation, temp file accumulation, and memory pressure build over weeks. Configure maintenance windows in the Cleaner's "Schedule" tab — ensure the window does not overlap with your active trading sessions or known high-volatility market events. See the FAQ for guidance on maintenance window timing relative to strategy operation.
Registry Optimization for Trader Machines
While registry cleaning has earned a questionable reputation in the consumer software market due to aggressive marketing of dubious benefits, the Windows Cleaner's registry module is conservatively scoped to entries that genuinely affect performance: dangling application references from uninstalled software, duplicate startup entries, and corrupted application path entries. On machines that have been running for 12+ months with significant software churn, this targeted optimization produces measurable improvement in application load times. The module runs a dry-run analysis by default — showing what would be modified — before any changes are applied.
Integrating Both Tools for Unattended Bot Operation
The full value of the free tools emerges when they operate together as an integrated maintenance and monitoring system. The recommended configuration for unattended bot operation:
- System Monitor: Enable the performance timeline, configure all four threshold alerts, and enable the startup watchdog. Set alerts to log-based (not notification-only) so they persist across sessions.
- Windows Cleaner: Schedule maintenance windows for 3:30am UTC daily (low-liquidity window, minimal trade impact). Enable bot log rotation with a 30-day retention policy for trade logs and a 7-day policy for system temp files.
- Combined review cadence: Weekly, review the System Monitor's performance timeline for anomalies that correlate with bot underperformance periods. Monthly, review the Windows Cleaner's log rotation report to verify log archiving is functioning and disk usage is within bounds.
Connecting Free Tools With Bot Performance Analysis
The DennTech free tools become significantly more valuable when their monitoring data is cross-referenced against bot trading performance. If the System Monitor logs a CPU spike at 03:15 UTC on a given night and your trade log — accessible through the monthly performance review process — shows two missed fills during that same window, you have identified a concrete optimization target. Reducing background processes during that window, scheduling Windows Update to run at a different time, or upgrading RAM eliminates the CPU contention and restores execution quality. This level of diagnosis is impossible without the System Monitor timeline data. Similarly, if the Windows Cleaner's log shows that temp files grew by 800MB over a single week, investigating what generated that growth — typically a runaway logging process or Windows Update staging — prevents the disk exhaustion that would eventually cause the bot's trade log database to become unwritable. See the bot setup guide for initial system configuration recommendations that minimize resource contention from the start, and review the first trade guide for how to verify the bot is executing correctly before leaving it unattended.
This configuration adds approximately 15 minutes of setup time but can prevent the class of unattended bot failures — disk full, memory exhaustion, process restart failures — that can translate into missed opportunities or unmonitored open positions during volatile market periods. The monthly performance review guide includes a system health checklist that integrates with these monitoring tools. For a full overview of all available DennTech free tools and how they complement the trading bot, visit the free apps page and review the documentation.