.svg){kind=small}
Finding Your Optimal Settings
While Bios provides excellent default settings for most use cases, every business need is unique. Sometimes you may want to find the absolute best settings for your specific situation through systematic testing.
When Default Settings Aren't Enough
The default settings work well for most scenarios, but if you're working on a critical application or have unique requirements, testing multiple configurations can help you squeeze out every bit of performance.
Why Test Different Settings?
Systematic testing helps you understand how different configurations affect your results and gives you confidence that you're using the best possible setup.
Maximize Performance
Find the exact configuration that produces the best results for your specific data and business requirements
Understand Sensitivity
Learn how robust your training is—whether small changes significantly impact results or if performance is stable
Build Confidence
Validate your configuration choices before investing in full-scale production deployment
How Systematic Testing Works
The process is straightforward: try multiple configurations, measure the results, and choose the best one.
Choose What to Test
Start with the most important setting—typically learning speed—since it has the biggest impact on training success. Focus on one setting at a time to clearly understand its effects.
Define Your Range
Test a reasonable range around the default value. Too narrow and you might miss the optimal setting; too wide and you waste resources on obviously bad configurations.
Example: If the default learning speed is set to medium, test very slow, slow, medium, fast, and very fast to see which performs best.
Run Parallel Tests
Instead of testing one configuration at a time sequentially, run multiple tests simultaneously. This dramatically reduces the total time needed to find your optimal settings.
Compare Results
Once all tests complete, compare their performance. Look for the configuration that achieves the best quality on your specific task.
Understanding Your Results
When you compare different configurations, you'll typically see a clear pattern emerge.
The Performance Curve
Most settings show a characteristic pattern where performance improves up to a point, then degrades:
Too Low
The model doesn't learn effectively. Training takes longer and may not reach good performance.
Just Right ✓
The sweet spot where the model learns efficiently and achieves the best final performance.
Too High
Training becomes unstable or the model "overshoot" and fails to converge properly.
Typical Performance Pattern
Your goal is to find the bottom of the curve—where performance is best
What Good Results Look Like
If your optimal setting is close to the default, that's great—it validates that the defaults are well-calibrated for your type of work. If it's significantly different, you've discovered a valuable optimization for your specific use case.
When to Invest in Testing
Systematic testing takes time and resources. Here's when it makes sense to invest in this process:
✓ Worth the Effort
- •You're deploying to production and need maximum confidence
- •The application is business-critical with low tolerance for errors
- •You'll be training many similar models and can reuse findings
- •Default settings aren't producing satisfactory results
- •You have specific performance targets to meet
⚠ Probably Overkill
- •You're just starting to explore fine-tuning
- •Default settings are already giving good results
- •You need a quick prototype or proof of concept
- •Time-to-deployment is more important than marginal improvements
- •This is a one-off training run
Testing Best Practices
Follow these guidelines to get the most value from your testing efforts:
Test One Thing at a Time
If you change multiple settings simultaneously, you won't know which change caused the performance difference. Focus on one setting, find the optimum, then move to the next.
Example: Optimize learning speed first, then use that optimal value while testing batch sizes.
Start from the Default
Bios's default settings are research-validated and work well for most cases. Use them as your starting point and test variations around them, rather than picking arbitrary values.
Use Enough Test Values
Too few test points and you might miss the optimum. Too many and you waste time. Generally, 5-7 well-chosen values are sufficient to find the best setting.
Document Your Findings
Record which configurations you tested and their results. This creates a knowledge base for future projects and helps you understand patterns in what works for your domain.
After Finding Optimal Settings
Once you've identified the best configuration for your needs:
Run Production Training
Use your optimal settings to train your final production model with your complete dataset.
Create a Baseline
Use these settings as your starting point for similar projects in the future, saving time on optimization.
Consider Other Settings
If you need even better performance, you can apply the same testing process to other settings like batch size or model capacity.
The Bottom Line
Systematic testing is a powerful tool for finding the absolute best configuration for your specific needs. However, it's not always necessary—Bios's defaults work well for most cases.
Consider testing when you need maximum performance or are deploying mission-critical applications. For most other scenarios, you can confidently use the defaults and focus on other aspects of your project.