Skip to content

Feature: Add Power and Fan Speed to Benchmark Results #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zorgoros wants to merge 12 commits into
base: main
Choose a base branch
from
+283 −147
Open

Feature: Add Power and Fan Speed to Benchmark Results #5

Show file tree
Hide file tree
Changes from 4 commits
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
32cdcae
feat(benchmark): Enhance data collection with power and fan speed; Re…
zorgoros Jul 8, 2025
99f8323
feat(cli): Add option to apply specific settings without benchmarking
zorgoros Jul 8, 2025
6b60b33
refactor(cli): Improve command-line help output
zorgoros Jul 8, 2025
6d19eb6
add new readme based on latest changes
zorgoros Jul 8, 2025
36c4fc1
add new readme based on latest changes
zorgoros Jul 9, 2025
44b2992
add new readme based on latest changes
zorgoros Jul 9, 2025
0604fac
add new readme based on latest changes
zorgoros Jul 9, 2025
7d4da38
fix(docs): Correct README argument inline code formatting
zorgoros Jul 10, 2025
9033a22
fix(docs): Correct README argument inline code formatting
zorgoros Jul 10, 2025
77a3cda
refining readme
zorgoros Jul 10, 2025
2edbeb4
refining readme
zorgoros Jul 11, 2025
fd3d302
refining readme
zorgoros Jul 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
311 changes: 162 additions & 149 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,166 +1,179 @@
# Bitaxe Hashrate Benchmark
# **Bitaxe Hashrate Benchmark**

A Python-based benchmarking tool for optimizing Bitaxe mining performance by testing different voltage and frequency combinations while monitoring hashrate, temperature, and power efficiency.

## Features
## **Features**

- Automated benchmarking of different voltage/frequency combinations
- Temperature monitoring and safety cutoffs
- Power efficiency calculations (J/TH)
- Automatic saving of benchmark results
- Graceful shutdown with best settings retention
- Docker support for easy deployment

## Prerequisites

- Python 3.11 or higher
- Access to a Bitaxe miner on your network
- Docker (optional, for containerized deployment)
- Git (optional, for cloning the repository)

## Installation

### Standard Installation

1. Clone the repository:
```bash
git clone https://github.com/mrv777/Bitaxe-Hashrate-Benchmark.git
cd Bitaxe-Hashrate-Benchmark
```

2. Create and activate a virtual environment:
```bash
python -m venv venv
# On Windows
venv\Scripts\activate
# On Linux/Mac
source venv/bin/activate
```

3. Install dependencies:
```bash
pip install -r requirements.txt
```

### Docker Installation

1. Build the Docker image:
```bash
docker build -t bitaxe-benchmark .
```

## Usage

### Standard Usage

Run the benchmark tool by providing your Bitaxe's IP address:

```bash
python bitaxe_hashrate_benchmark.py <bitaxe_ip>
```

Optional parameters:
- `-v, --voltage`: Initial voltage in mV (default: 1150)
- `-f, --frequency`: Initial frequency in MHz (default: 500)

Example:
```bash
python bitaxe_hashrate_benchmark.py 192.168.2.29 -v 1175 -f 775
```

### Docker Usage (Optional)

Run the container with your Bitaxe's IP address:

```bash
docker run --rm bitaxe-benchmark <bitaxe_ip> [options]
```

Example:
```bash
docker run --rm bitaxe-benchmark 192.168.2.26 -v 1200 -f 550
```

## Configuration

The script includes several configurable parameters:

- Maximum chip temperature: 66°C
- Maximum VR temperature: 86°C
- Maximum allowed voltage: 1400mV
- Minimum allowed voltage: 1000mV
- Maximum allowed frequency: 1200MHz
- Maximum power consumption: 40W
- Minimum allowed frequency: 400MHz
- Minimum input voltage: 4800mV
- Maximum input voltage: 5500mV
- Benchmark duration: 10 minutes
- Sample interval: 15 seconds
- **Minimum required samples: 7** (for valid data processing)
- Voltage increment: 20mV
- Frequency increment: 25MHz

## Output

The benchmark results are saved to `bitaxe_benchmark_results_<ip_address>.json`, containing:
- Complete test results for all combinations
- Top 5 performing configurations ranked by hashrate
- Top 5 most efficient configurations ranked by J/TH
- For each configuration:
- Average hashrate (with outlier removal)
- Temperature readings (excluding initial warmup period)
- VR temperature readings (when available)
- Power efficiency metrics (J/TH)
- Input voltage measurements
- Voltage/frequency combinations tested

## Safety Features

- Automatic temperature monitoring with safety cutoff (66°C chip temp)
- Voltage regulator (VR) temperature monitoring with safety cutoff (86°C)
- Input voltage monitoring with minimum threshold (4800mV) and maximum threshold (5500mV)
- Power consumption monitoring with safety cutoff (40W)
- Temperature validation (must be above 5°C)
- Graceful shutdown on interruption (Ctrl+C)
- Automatic reset to best performing settings after benchmarking
- Input validation for safe voltage and frequency ranges
- Hashrate validation to ensure stability
- Protection against invalid system data
- Outlier removal from benchmark results

## Benchmarking Process
* Automated benchmarking of different voltage/frequency combinations
* **Direct setting of specific voltage and frequency from command line**
* Temperature monitoring and safety cutoffs
* **Power consumption monitoring and reporting (Watts)**
* **Fan speed monitoring and reporting (RPM/Percentage)**
* Power efficiency calculations (J/TH)
* Automatic saving of benchmark results
* Graceful shutdown with best settings retention
* Docker support for easy deployment

## **Prerequisites**

* Python 3.11 or higher
* Access to a Bitaxe miner on your network
* Docker (optional, for containerized deployment)
* Git (optional, for cloning the repository)

## **Installation**

### **Standard Installation**

1. Clone the repository:
git clone https://github.com/mrv777/Bitaxe-Hashrate-Benchmark.git
cd Bitaxe-Hashrate-Benchmark

2. Create and activate a virtual environment:
python \-m venv venv
\# On Windows
venv\\Scripts\\activate
\# On Linux/Mac
source venv/bin/activate

3. Install dependencies:
pip install \-r requirements.txt

### **Docker Installation**

1. Build the Docker image:
docker build \-t bitaxe-benchmark .

## **Usage**

### **Standard Usage (Run Full Benchmark)**

Run the benchmark tool by providing your Bitaxe's IP address and initial settings:
python bitaxe\_hasrate\_benchmark.py \<bitaxe\_ip\> \-v \<initial\_voltage\> \-f \<initial\_frequency\>

**Arguments:**

* \<bitaxe\_ip\>: **Required.** IP address of your Bitaxe miner (e.g., 192.168.2.26).
* \-v, \--voltage: **Optional.** Initial voltage in mV for testing (default: 1150).
* \-f, \--frequency: **Optional.** Initial frequency in MHz for testing (default: 500).

**Example:**
python bitaxe\_hasrate\_benchmark.py 192.168.1.136 \-v 1150 \-f 500

### **Apply Specific Settings (Without Benchmarking)**

To quickly apply specific voltage and frequency settings to your Bitaxe without running the full benchmark:
python bitaxe\_hasrate\_benchmark.py \<bitaxe\_ip\> \--set-values \-v \<desired\_voltage\_mv\> \-f \<desired\_frequency\_mhz\>

**Arguments:**

* \<bitaxe\_ip\>: **Required.** IP address of your Bitaxe miner.
* \-s, \--set-values: **Flag.** Activates this mode to only set values and exit.
* \-v, \--voltage: **Required.** The exact voltage in mV to apply.
* \-f, \--frequency: **Required.** The exact frequency in MHz to apply.

**Example:**
python bitaxe\_hasrate\_benchmark.py 192.168.1.136 \--set-values \-v 1150 \-f 780

### **Docker Usage (Optional)**

Run the container with your Bitaxe's IP address (add \--set-values for that mode):
docker run \--rm bitaxe-benchmark \<bitaxe\_ip\> \[options\]

Example (Full Benchmark):
docker run \--rm bitaxe-benchmark 192.168.2.26 \-v 1200 \-f 550

Example (Set Settings Only):
docker run \--rm bitaxe-benchmark 192.168.2.26 \--set-values \-v 1150 \-f 780

## **Configuration**

The script includes several configurable parameters. These can be adjusted in the bitaxe\_hasrate\_benchmark.py file:

* Maximum chip temperature: 66°C
* Maximum VR temperature: 86°C
* Maximum allowed voltage: 1400mV
* Minimum allowed voltage: 1000mV
* Maximum allowed frequency: 1200MHz
* Maximum power consumption: 30W
* Minimum allowed frequency: 400MHz
* Minimum input voltage: 4800mV
* Maximum input voltage: 5500mV
* Benchmark duration: 600 seconds (10 minutes per combination)
* Sample interval: 15 seconds
* Minimum required samples: 7 (for valid data processing)
* Voltage increment: 15mV
* Frequency increment: 20MHz
* **ASIC Configuration:** asic\_count is hardcoded to 1 as it's not always provided by the API. small\_core\_count is fetched from the Bitaxe.

## **Output**

The benchmark results are saved to bitaxe\_benchmark\_results\_\<ip\_address\>.json, containing:

* Complete test results for all combinations
* Top 5 performing configurations ranked by hashrate
* Top 5 most efficient configurations ranked by J/TH
* For each configuration:
* Average hashrate (with outlier removal)
* Temperature readings (excluding initial warmup period)
* VR temperature readings (when available)
* Power efficiency metrics (J/TH)
* **Average Power (Watts)**
* **Average Fan Speed (Percentage or RPM, if available from API)**
* Input voltage measurements
* Voltage/frequency combinations tested
* Error reason (if any) for a specific iteration

## **Safety Features**

* Automatic temperature monitoring with safety cutoff (66°C chip temp)
* Voltage regulator (VR) temperature monitoring with safety cutoff (86°C)
* Input voltage monitoring with minimum threshold (4800mV) and maximum threshold (5500mV)
* Power consumption monitoring with safety cutoff (30W)
* Temperature validation (must be above 5°C)
* Graceful shutdown on interruption (Ctrl+C)
* Automatic reset to best performing settings after benchmarking
* Input validation for safe voltage and frequency ranges
* Hashrate validation to ensure stability
* Protection against invalid system data
* Outlier removal from benchmark results

## **Benchmarking Process**

The tool follows this process:
1. Starts with user-specified or default voltage/frequency
2. Tests each combination for 20 minutes
3. Validates hashrate is within 8% of theoretical maximum
4. Incrementally adjusts settings:
- Increases frequency if stable
- Increases voltage if unstable
- Stops at thermal or stability limits
5. Records and ranks all successful configurations
6. Automatically applies the best performing stable settings
7. Restarts system after each test for stability

1. Starts with user-specified or default voltage/frequency
2. Tests each combination for 10 minutes
3. Validates hashrate is within 8% of theoretical maximum
4. Incrementally adjusts settings:
* Increases frequency if stable
Copy link

@coderabbitai coderabbitai bot Jul 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Inconsistent hashrate-validation thresholds (8 % vs 6 %)

Section “Benchmarking Process” states the tool validates hashrate within 8 % of the theoretical maximum (l. 167), whereas “Data Processing” lists a 6 % threshold (l. 183).
Readers (and future maintainers) cannot tell which rule is authoritative.

-3. Validates hashrate is within 8% of theoretical maximum  
+3. Validates hashrate is within 6% of theoretical maximum

Alternatively, change the “Data Processing” bullet to 8 %; just make them match.

Also applies to: 181-184

🤖 Prompt for AI Agents 
In README.md around lines 165 to 169 and 181 to 184, the hashrate validation
thresholds are inconsistent, showing 8% in the Benchmarking Process section and
6% in the Data Processing section. To fix this, update the threshold in the Data
Processing section to 8% so both sections match and clearly communicate the
authoritative validation rule.

* Increases voltage if unstable
* Stops at thermal or stability limits
5. Records and ranks all successful configurations
6. Automatically applies the best performing stable settings
7. Restarts system after each test for stability
8. Allows 90-second stabilization period between tests

## Data Processing
## **Data Processing**

The tool implements several data processing techniques to ensure accurate results:
- Removes 3 highest and 3 lowest hashrate readings to eliminate outliers
- Excludes first 6 temperature readings during warmup period
- Validates hashrate is within 6% of theoretical maximum
- Averages power consumption across entire test period
- Monitors VR temperature when available
- Calculates efficiency in Joules per Terahash (J/TH)

## Contributing
* Removes 3 highest and 3 lowest hashrate readings to eliminate outliers
* Excludes first 6 temperature readings during warmup period
* Validates hashrate is within 6% of theoretical maximum
* Averages power consumption across entire test period
* Monitors VR temperature when available
* Calculates efficiency in Joules per Terahash (J/TH)
* **Averages fan speed across entire test period**

## **Contributing**

Contributions are welcome! Please feel free to submit a Pull Request.
Contributions are welcome\! Please feel free to submit a Pull Request.

## License
## **License**

This project is licensed under the GNU General Public License v3.0 - see the [LICENSE](LICENSE) file for details.
This project is licensed under the GNU General Public License v3.0 \- see the [LICENSE](https://www.google.com/search?q=LICENSE) file for details.

## Disclaimer
## **Disclaimer**

Please use this tool responsibly. Overclocking and voltage modifications can potentially damage your hardware if not done carefully. Always ensure proper cooling and monitor your device during benchmarking.
Loading