The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Set innodb_io_capacity close to the number of sustained I/O operations per second your storage can deliver to the actual InnoDB workload—not the peak IOPS printed by a drive vendor. Keep the value as low as practical while still allowing dirty-page flushing, checkpoint work, and insert-buffer activity to keep up. Set innodb_io_capacity_max at least as high as the base value; using roughly twice the base is a documented starting point when flushing falls behind. Validate both values with representative traffic, latency, dirty pages, checkpoint age, and innodb_log_waits.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
What innodb_io_capacity controls
MySQL defines innodb_io_capacity as the overall I/O capacity available to InnoDB. In practice, it is the target rate InnoDB uses for background work such as flushing dirty pages, advancing checkpoints, and processing change-buffer (insert-buffer) merges. The setting is expressed in I/O operations per second (IOPS), not megabytes per second.
As an Amazon Associate I earn from qualifying purchases.
The value is a budget for InnoDB background activity, not a promise that the server will issue exactly that many operations every second. Foreground reads and writes, redo logging, binary-log work, the operating system, and other services also consume storage bandwidth and queue depth. Your setting therefore has to fit the capacity left for InnoDB after those demands are considered.
Oracle’s guidance is to set the variable approximately to the number of I/O operations the system can perform per second and to keep it as low as practical without allowing background activity to fall behind. A low value that leaves a growing checkpoint or dirty-page backlog is harmful; a value that is unnecessarily high can flush pages too aggressively and reduce the benefit of the buffer pool.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
innodb_io_capacity versus innodb_io_capacity_max
| Variable | Role | How to use it |
|---|---|---|
innodb_io_capacity |
Normal background-flushing and maintenance rate. | Set near the sustainable IOPS budget available to InnoDB, after leaving room for foreground work and other services. |
innodb_io_capacity_max |
Higher rate InnoDB may use when normal flushing cannot keep up. | Never set it below the base value. A value about twice the base is a documented starting point when flushing falls behind, then verify the effect on latency and storage saturation. |
These variables do not cap every I/O issued by the server. Checkpoint pressure can make InnoDB flush at a higher rate than the base value, and some settings can allow a checkpoint burst to bypass the configured rate. Treat the numbers as control points for background work rather than strict traffic shapers.
Check your MySQL version and current settings first
Defaults have changed between releases, so never infer the active value from a blog post or from another server. Run this query on the instance you intend to tune:
SELECT @@version, @@innodb_io_capacity, @@innodb_io_capacity_max;The current MySQL 26.7 Reference Manual documents a minimum value of 100 and a default of 10,000. The MySQL 8.0 Reference Manual documents a default of 200 and uses 100 as an example for an individual 5,400- or 7,200-RPM disk. Those figures are documentation defaults and examples, not recommendations for every installation. A server upgraded between release families can therefore retain a value that is very different from what you expected.
| Documentation context | Documented value | Interpretation |
|---|---|---|
| Current MySQL 26.7 Reference Manual | 10,000 default | Default documented for that release; inspect the running server rather than assuming it applies to an older release. |
| Current MySQL 26.7 Reference Manual | 100 minimum | Values below 100 are not valid for innodb_io_capacity. |
| MySQL 8.0 Reference Manual | 200 default | Default documented for the 8.0 manual. |
| MySQL 8.0 Reference Manual | 100 example | Example given for an individual 5,400/7,200-RPM drive, not a universal disk setting. |
Also check whether the server is using a configuration file, an included configuration fragment, or an orchestration layer that will overwrite a runtime change at restart. Record the current values before changing them so that a test can be reversed cleanly.
Measure the IOPS InnoDB can really sustain
The useful input is sustained random-write performance through the same storage path and operating conditions that production uses. A short synthetic peak can make a storage system look much faster than it is during a long checkpoint or flush cycle.
- Use the production storage path. Measure the same data volume, controller, virtual-disk mapping, filesystem, and host path used by the InnoDB tablespace and redo logs. A benchmark on a different device does not establish the capacity available to this server.
- Match block-size characteristics. Use I/O sizes that resemble the workload you are tuning. IOPS changes with request size, so a result measured with one block size cannot be transferred unchanged to another.
- Match concurrency and queueing. Use a realistic number of concurrent operations. A device can report a high maximum at a queue depth that your database never reaches, while latency at that queue depth may be unacceptable.
- Include the durability settings that matter. Fsync behavior and other durability choices alter both throughput and latency. Measure with settings that resemble production rather than with a relaxed benchmark profile.
- Run long enough to expose steady-state behavior. Record the sustained result after caches and device-level burst buffers stop flattering the measurement. Note throughput, read/write mix, and latency, not just a single IOPS number.
- Account for competing activity. The capacity available to InnoDB is what remains after foreground queries, redo, binary logging, backups, replication work, and other services use the storage. If those consumers vary by time of day, measure the busiest representative period.
Vendor specifications are useful as an upper reference, but they are not an automatic value for the variable. They often describe a narrow test condition and do not include your filesystem, controller, workload mix, or competing traffic. If you only have a vendor number, treat it as a ceiling to investigate, not as a setting to deploy.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Turn the measurement into a starting value
Start with the sustainable IOPS budget that is actually available to InnoDB. In symbolic form:
InnoDB budget ≈ sustained storage IOPS − IOPS reserved for foreground and other services
The subtraction is a planning concept, not a fixed percentage supplied by MySQL. Leave enough headroom for normal query traffic, redo, binary logging, and transient variation. If you allocate the entire laboratory maximum to background flushing, foreground latency can rise as soon as users or other services need the device.
For example, if a representative test establishes that 6,000 IOPS can be devoted to InnoDB background work while preserving the required foreground latency, a reasonable first test is innodb_io_capacity=6000. Set innodb_io_capacity_max no lower than 6,000; 12,000 (twice the base) is a documented starting point for a system that needs a higher catch-up rate. Those numbers are an illustration of the method, not a claim about your hardware.
Recommended Free Tools
Do not chase a larger number simply because the storage device advertises one. Raise the base only when observations show that background work is falling behind and the storage still has safe latency and utilization headroom. Lower it when flushing is not behind and the higher rate is competing unnecessarily with foreground activity.
Apply a reversible change
Runtime changes let you observe behavior without committing a configuration file immediately. The account must have privileges sufficient to set global system variables.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
- Capture the current values with
SELECT @@version, @@innodb_io_capacity, @@innodb_io_capacity_max;. - Set the normal background rate:
SET GLOBAL innodb_io_capacity = 6000;- When a higher catch-up rate is justified, set the maximum to a value at least as high as the base:
SET GLOBAL innodb_io_capacity_max = 12000;- Verify the values from a new session and record the change time, workload conditions, and reason for the test.
- Observe representative traffic through normal peaks and checkpoint activity. Do not persist a value based only on the first few minutes after the change.
- After the setting has behaved acceptably across a restart plan, place the chosen values in the server’s
my.cnformy.iniconfiguration. Keep the runtime and persistent values aligned so a restart does not silently restore an older rate.
If the runtime statement fails, check the account’s global-variable privileges and confirm that the variable is available in the server version. If a restart reverts a successful test, inspect all configuration files and startup parameters for a second definition.
Measure whether the setting is helping
Use the same workload before and after a change. The important comparison is not just storage throughput; it is whether InnoDB completes background work without causing unacceptable foreground latency.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute| What to watch | What a healthy result looks like | What a warning suggests |
|---|---|---|
| Dirty-page percentage | Dirty pages are flushed at a rate that prevents a persistent or accelerating backlog. | A rising percentage means background flushing may be under-provisioned or the workload has changed. |
| Checkpoint age | Redo checkpoint age remains within the range the workload can sustain without forcing urgent flushing. | Periodic growth followed by urgent flushes points to insufficient normal capacity or a burst condition. |
| History-list length | It does not grow continually under the test workload. | A growing list can indicate that purge-related work is not keeping up; investigate alongside I/O symptoms rather than changing this variable blindly. |
| Insert-buffer merges | Merges progress without creating a persistent maintenance queue. | A backlog indicates that background work may be constrained. |
| Write throughput and latency | Foreground throughput and latency remain within the service target while flushing progresses. | Latency spikes after raising the value can mean the setting is consuming too much shared storage capacity. |
innodb_log_waits |
No new waits, or no worsening compared with the baseline. | Increases indicate pressure around redo-log space or flushing and deserve investigation. |
| Storage saturation | Device utilization and latency remain inside the limits established for the workload. | Saturation with little foreground benefit is a reason to reduce the rate or reserve more headroom. |
MySQL recommends increasing capacity when checkpoint flushing produces periodic throughput drops. It recommends lowering the setting when flushing is not falling behind. Make one controlled change at a time, then compare the same metrics under similar traffic so that a workload change is not mistaken for a tuning result.
Why flushing can still happen in bursts
Checkpoint pressure can exceed the base rate
When flushing falls behind, InnoDB can flush more aggressively at a higher IOPS rate than the value configured in innodb_io_capacity. That behavior is intentional: allowing the backlog to grow indefinitely would eventually force more disruptive work. The maximum setting provides a higher rate for this catch-up behavior, so a server can appear to ignore the base value during a checkpoint emergency.
innodb_flush_sync can bypass the configured rate
innodb_flush_sync is enabled by default. During checkpoint bursts it can cause the configured capacity to be ignored, which is why an otherwise moderate setting may still coincide with a sudden write spike. Disable it only when strict adherence to the configured rates is a specific requirement and you have evaluated the resulting checkpoint behavior, latency, and backlog. Turning it off is not a general remedy for an undersized or overloaded storage system.
The base value may be too low for the workload
If dirty pages, checkpoint age, or periodic throughput dips worsen between bursts, the issue may simply be that normal background work cannot keep up. Raising the base toward the sustainable InnoDB budget can reduce the size and frequency of catch-up events, provided the storage has headroom. Raising the maximum alone can make emergency bursts faster without fixing the steady-state backlog.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
The storage result may not represent production
A setting based on a short, high-queue-depth benchmark can look correct until a long write-heavy period, a different read/write mix, or a competing backup consumes the same device. Re-measure under representative conditions before concluding that MySQL is disregarding the setting.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Balance flushing against cache benefit and query latency
A higher capacity has a clear benefit when write-heavy activity is creating a checkpoint backlog: more dirty pages can be written before the backlog turns into a throughput dip. The cost is that those writes compete with foreground I/O. If the rate is too high, pages can be flushed aggressively even when the workload does not need it, reducing the buffer pool’s cache benefit and increasing storage contention.
- Prefer the lower value when dirty pages and checkpoint age remain controlled, foreground latency is stable, and no periodic flushing dip appears.
- Move upward cautiously when checkpoint flushing causes recurring throughput drops or the background queue grows during representative traffic.
- Use a higher maximum for recovery from a backlog only when the device can absorb the extra I/O without violating latency targets.
- Back off when storage latency rises, foreground throughput falls, or the observed flush rate is clearly consuming capacity without reducing the backlog.
There is no universal SSD, RAID, or cloud-volume value. Two devices marketed with the same peak IOPS can provide different sustained performance once request size, concurrency, durability, filesystem behavior, and competing traffic are included. Tune the server to measured behavior, not to the storage label.
Practical profiles by storage type
Individual rotational disk
The MySQL 8.0 manual’s value of 100 is an example for an individual 5,400- or 7,200-RPM drive. Use it as documentation context, not as proof that every rotational disk should be set to 100. Measure the actual path and workload; a busy drive shared with other services may have less capacity available, while a dedicated path may sustain a different rate.
Free tools Windows power users keep installed
One-click scans. No signup required.
SSD or flash-backed volume
Do not copy a vendor’s headline IOPS number directly into the variable. Establish sustained random-write performance with production-like request sizes, concurrency, durability, and read/write mix, then reserve capacity for foreground activity and other services. Flash devices can also show burst behavior, making a long steady-state measurement especially important.
RAID or shared storage
Measure through the complete RAID or virtual-storage path. Controller caches, parity work, multipath configuration, and other tenants can change both IOPS and latency seen by MySQL. The value to use is the sustainable budget delivered to this InnoDB instance, not the sum of the individual device specifications.
A repeatable tuning loop
- Baseline. Record the MySQL version, current capacity values, workload mix, foreground latency, dirty pages, checkpoint age, history-list length, insert-buffer merges, write throughput, storage latency, and
innodb_log_waits. - Measure. Run a sustained, production-like random-write test through the real storage path and document the conditions and result.
- Choose a conservative base. Allocate only the IOPS that can be given to InnoDB after foreground and competing work are accounted for. Keep the value at or above the documented minimum of 100.
- Choose the maximum. Set
innodb_io_capacity_maxno lower than the base. If a backlog is observed, twice the base is a documented starting point; it is not a mandatory ratio. - Change at runtime. Use
SET GLOBALso the test is reversible, and confirm the new values. - Exercise the real workload. Include the write-heavy periods that previously produced checkpoint dips or flushing bursts.
- Compare the evidence. Keep the change only if backlog indicators improve without unacceptable latency or storage saturation.
- Persist and document. Once the result survives representative traffic and a restart plan, update
my.cnformy.ini, note the rationale, and retain the previous values for rollback.
Troubleshooting common outcomes
“The value is high, but checkpoint age still grows”
Confirm that the measured IOPS budget was sustainable and available to InnoDB rather than a short benchmark peak. Check whether foreground traffic or another service is consuming the device. Review dirty pages, checkpoint age, storage latency, and innodb_log_waits. If the backlog is real and latency headroom remains, increase the base in a controlled step; do not assume that increasing only the maximum solves steady-state under-capacity.
“Raising the value made queries slower”
The new rate may be competing with foreground reads and writes. Compare storage latency and foreground response time with the baseline. Reduce the base, restore more headroom for user traffic, or retain a lower normal rate while using a carefully evaluated maximum for catch-up.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute“The server still shows I/O spikes even though the base is low”
Check innodb_flush_sync, which is enabled by default and can allow checkpoint bursts to ignore the configured rate. Also check whether InnoDB is recovering from a backlog and therefore using the higher maximum. A burst is not automatically evidence that the variable failed.
“A runtime change disappeared after reboot”
SET GLOBAL changes the running server. Persist the chosen values in my.cnf or my.ini only after validation, and inspect included files or startup automation for conflicting definitions. Re-run the version and variable query after restart.
“Can I set a value below 100 to reduce load?”
No. The current MySQL 26.7 Reference Manual documents 100 as the minimum for innodb_io_capacity. To reduce background pressure, measure whether a value near that minimum is sufficient and address competing storage work rather than using an invalid value.
Decision checklist
- Have you checked
@@versionand the active values instead of assuming a release default? - Was the IOPS measurement sustained and made through the same storage path as production?
- Did the test match request size, concurrency, durability, and read/write mix?
- Did you reserve capacity for foreground queries, redo, binary logging, and other services?
- Is
innodb_io_capacity_maxat least as high as the base value? - Did you compare dirty pages, checkpoint age, history-list length, insert-buffer merges, throughput, latency, storage saturation, and
innodb_log_waitsbefore and after? - Did you account for the default behavior of
innodb_flush_syncwhen interpreting bursts? - Have you tested the setting through a representative write-heavy period and verified what happens after restart?
The practical answer
Use measured, sustainable IOPS as the starting point for innodb_io_capacity, then reduce that number as needed to leave room for foreground work. Keep innodb_io_capacity_max no lower than the base and consider twice the base when a measured backlog needs a faster catch-up rate. Judge the result by checkpoint and dirty-page behavior together with user-facing latency. If bursts remain, investigate checkpoint pressure and the default innodb_flush_sync behavior before assuming the configured capacity is being ignored.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
