MySQL Cost Optimization
Cut your MySQL bill from the inside. OhChimp finds unused indexes, fragmented tables, and buffer pool waste, then writes fixes verified on your real bill.
How does OhChimp connect to MySQL?
OhChimp connects with a database username and password, with optional SSL/TLS. It opens a read-only session with a 30-second query timeout and runs probe queries against catalog and statistics views like information_schema, performance_schema, and the sys schema. It works with self-hosted and managed MySQL.
Does OhChimp need write access or see my data?
No. OhChimp runs in a read-only session and reads schema, index, and engine statistics, never your application rows. At connect time it checks your grants and warns you if it sees INSERT, UPDATE, or DELETE privileges, so you can switch to a read-only user. It never stores your application data, secrets, or workload contents.
What MySQL costs can OhChimp actually reduce?
The ones a cloud billing dashboard never exposes: unused and redundant indexes, fragmented table space you can reclaim with OPTIMIZE TABLE, a buffer pool hit ratio that signals over- or under-sized memory, queries doing full table scans, tables over 10 GB that should be partitioned, and oversized binary logs or idle replicas.
Who applies the changes, and can they be rolled back?
You do. Each fix is a reviewable plan with a confidence score, a risk level, and rollback steps. Nothing changes until you click apply, and OhChimp applies the matching code and infrastructure changes together.
How are MySQL savings verified, and what does it cost?
Savings are checked against your real bill. A plan is marked VERIFIED only after 7 or more days, a drop of at least 10%, and 3 consecutive positive checks. Until then it stays flagged not implemented. Pricing is a flat monthly fee with no cut of your savings, plus a year-one ROI guarantee: a full refund of subscription fees if it does not pay for itself in your first 12 months on a paid plan.