Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →ProxySQL sits between your application and one or more MySQL servers. Applications connect to ProxySQL through its MySQL traffic listener, while ProxySQL chooses a backend from configured hostgroups, applies health and replication state, and can route selected reads to replicas. On a normal installation, the Admin interface is at 127.0.0.1:6032 and the MySQL traffic listener is commonly 6033.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
The reliable operating pattern is: install and start ProxySQL, configure backends in mysql_servers, create a least-privilege monitor account, define writer and reader hostgroups when replication is present, register application credentials, add narrowly scoped query rules, then load every change into runtime and save it to disk. If you edit only the main tables, the worker threads do not use the change, and an unsaved change disappears after a restart.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →What ProxySQL does in a MySQL topology
ProxySQL is a MySQL-compatible proxy, not a replacement for MySQL replication. Your application opens its database connections to ProxySQL. ProxySQL maintains backend connection pools to the MySQL servers and selects a destination according to hostgroup membership, user defaults, query rules, server status, connection limits, and monitoring results.
A simple deployment might have one ProxySQL node in front of a primary and two replicas. The primary handles writes. Replicas handle eligible reads. A more elaborate deployment can use more than one ProxySQL node, but that adds configuration synchronization, failure-domain, and operational considerations rather than removing them.
#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.
| Purpose | Typical endpoint or object | What it controls |
|---|---|---|
| ProxySQL Admin | 127.0.0.1:6032 using the MySQL protocol |
Servers, users, query rules, variables, runtime state, and persisted configuration |
| ProxySQL Admin over PostgreSQL protocol | 6132 |
Documented alternative Admin protocol |
| Application traffic | Commonly 6033 |
Connections and SQL sent toward backend MySQL servers |
| Backend MySQL | Usually port 3306 |
The actual database nodes registered in hostgroups |
Port 6033 is the documented default shown in the configuration example; verify the listener in your own configuration before changing an application. Port 6032 is for administration, not normal application traffic. Keep it on a management interface and do not expose it broadly.
Prerequisites and a safe topology
Before configuring routing, make sure the Ubuntu host can resolve and reach every MySQL backend on its MySQL port. Decide which hostgroup represents writers and which represents readers. In the examples below, hostgroup 1 is the writer group and hostgroup 2 is the reader group.
Recommended Free Tools
- Install a ProxySQL package that matches your Ubuntu release and architecture.
- Have network access from ProxySQL to each backend, including firewall rules and DNS or stable IP addresses.
- Create a dedicated MySQL monitor account on every backend. Do not reuse an application administrator account.
- Ensure the application account exists both in MySQL and in ProxySQL’s
mysql_userstable. - Document whether your application uses transactions, session variables, temporary tables, stored procedures, or read-after-write behavior. Those details determine which reads can safely move to replicas.
- Choose replacement secrets before production. The example passwords in documentation and this guide are placeholders, not credentials to deploy.
If you have only one MySQL server, ProxySQL can still provide a consistent client endpoint and connection pooling, but it cannot create high availability by itself. Load balancing becomes meaningful when multiple healthy backend nodes are available.
Install and start ProxySQL on Ubuntu
Use the ProxySQL package appropriate for your Ubuntu release, then start the service with the system service manager. Package names and repository instructions vary by release, so use the package source approved for your environment rather than copying a repository line intended for a different Ubuntu version.
- Install the ProxySQL package and its service definition.
- Start the service with
service proxysql start. - Confirm that the process is running and check the installed binary with
proxysql --version. - Use
service proxysql stopto stop it orservice proxysql restartafter a controlled configuration change that requires a process restart.
An example version displayed in current ProxySQL documentation is v3.0.5, codename Truls. That is an example of documentation output, not a guarantee that every Ubuntu package currently installs that version. Record the version actually installed on your host when documenting an environment.
On the first startup, ProxySQL initializes and uses its SQLite database. The main configuration file, commonly /etc/proxysql.cnf, is not the continuing source of truth for changes made through the Admin interface. Treat the Admin database layers described below as authoritative after initialization.
Connect to the Admin interface
The documented MySQL-protocol Admin connection is:
mysql -u admin -padmin -h 127.0.0.1 -P6032 --prompt='Admin> 'Replace the example password immediately. If you use MySQL client 8.4 or later and authentication negotiation requires it, add --default-auth=mysql_native_password to the client command.
ProxySQL also documents a PostgreSQL-protocol Admin interface on port 6132. Most MySQL administration examples use port 6032, so make sure your client and protocol match the listener you selected.
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.
For production, bind Admin access to localhost or a restricted management network, protect the account, and place any remote access behind your normal administrative controls. Never point application connection strings at the Admin port.
Add MySQL backends to hostgroups
Hostgroups are ProxySQL’s routing units. A query rule or user default points to a hostgroup, and ProxySQL chooses an eligible server within that group. Add each backend to the appropriate hostgroup in mysql_servers:
INSERT INTO mysql_servers(hostgroup_id,hostname,port)
VALUES (1,'10.0.0.1',3306);
INSERT INTO mysql_servers(hostgroup_id,hostname,port)
VALUES (1,'10.0.0.2',3306);
LOAD MYSQL SERVERS TO RUNTIME;
SAVE MYSQL SERVERS TO DISK;The example places both servers in hostgroup 1. For a primary-and-replica topology, you can initially register all nodes and then let replication-hostgroup monitoring place them into writer or reader groups, or register them directly in the groups that match your design.
Server attributes that affect routing
| Attribute | Effect | Operational use |
|---|---|---|
weight |
Distributes traffic proportionally among servers in one hostgroup. | Give a larger-capacity node a higher share, but validate that the difference reflects real capacity. |
max_connections |
Limits ProxySQL’s backend connections to that server. | Protect a database from connection storms and keep the limit compatible with MySQL capacity. |
status |
Can be ONLINE, OFFLINE_SOFT, or OFFLINE_HARD. |
Use a soft drain for maintenance when existing connections should finish; use hard offline to stop service immediately. |
max_replication_lag |
Can remove a lagging replica from service when its lag exceeds the configured threshold. | Set a threshold that protects read freshness without ejecting replicas for harmless short spikes. |
After inserting or editing rows, LOAD MYSQL SERVERS TO RUNTIME activates them for worker threads. SAVE MYSQL SERVERS TO DISK persists them across a restart. Running only the first command creates a working but temporary configuration.
Create a dedicated monitor account
ProxySQL’s health checks need credentials that can connect and inspect replication state. Create a monitor account in MySQL on each backend:
CREATE USER 'monitor' IDENTIFIED BY 'replace-with-a-secret';
GRANT USAGE, REPLICATION CLIENT ON *.* TO 'monitor';Use the same username and an appropriately protected secret on every backend that ProxySQL must monitor. The account is for health and state checks, not for application queries. Follow your MySQL version’s account-host policy when creating it; the important properties are a dedicated identity and the minimum privileges required for the checks.
Configure monitor intervals
Set the monitor credentials and polling intervals in ProxySQL’s global_variables table:
UPDATE global_variables SET variable_value='monitor'
WHERE variable_name='mysql-monitor_username';
UPDATE global_variables SET variable_value='replace-with-a-secret'
WHERE variable_name='mysql-monitor_password';
UPDATE global_variables SET variable_value='2000'
WHERE variable_name IN ('mysql-monitor_connect_interval',
'mysql-monitor_ping_interval',
'mysql-monitor_read_only_interval');
LOAD MYSQL VARIABLES TO RUNTIME;
SAVE MYSQL VARIABLES TO DISK;The value 2000 is an interval setting in milliseconds for the documented example. Choose polling intervals with awareness of backend count, network latency, and how quickly you need to react to failure. Very aggressive polling increases monitoring traffic; very slow polling delays detection.
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
While bringing the pool online, inspect monitor.mysql_server_connect_log, monitor.mysql_server_ping_log, and monitor.mysql_server_read_only_log. These logs distinguish authentication failures, unreachable hosts, ping failures, and an unexpected read_only state.
Separate writers and readers with replication hostgroups
For a primary plus replicas, define a writer hostgroup and a reader hostgroup:
INSERT INTO mysql_replication_hostgroups
(writer_hostgroup,reader_hostgroup,comment)
VALUES (1,2,'cluster1');
LOAD MYSQL SERVERS TO RUNTIME;ProxySQL uses MySQL’s read_only value to classify servers: read_only=0 is treated as a writer and read_only=1 as a reader. The monitor moves servers between the configured hostgroups as the observed state changes. Confirm the placement in monitor.mysql_server_read_only_log instead of assuming that a server’s role is correct.
This mechanism depends on the database topology actually maintaining reliable read_only values. If a failover tool changes roles, make sure the new primary and replicas expose the state that ProxySQL is monitoring and that replication is healthy before sending production traffic.
Decide what can be read from replicas
Replication-aware routing does not make every SELECT safe to send away from the writer. A replica can be behind, and a transaction may need to read data written earlier in the same session. Statements involving temporary tables, session state, locks, or procedures may also depend on a specific connection and server.
A conservative design keeps the application user’s default hostgroup on the writer and adds narrowly scoped rules for known, replica-safe reads. This favors correctness over maximum replica utilization. Broader read routing can be considered only after you understand transaction boundaries, acceptable replica lag, and read-after-write requirements.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRegister the application user
The application credential must exist in MySQL and in ProxySQL. Add it to mysql_users with a writer fallback:
INSERT INTO mysql_users(username,password,default_hostgroup)
VALUES ('appuser','replace-with-a-secret',1);
LOAD MYSQL USERS TO RUNTIME;
SAVE MYSQL USERS TO DISK;default_hostgroup is where traffic goes when no query rule matches. Setting it to the writer group keeps unmatched statements on the safe path. Grant the user only the schemas and operations the application needs in MySQL. Do not use the monitor account for application traffic, and do not reuse documentation passwords.
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.
Write ordered, specific query rules
ProxySQL evaluates query rules in ascending rule_id order. A rule can match a username, digest, or other query properties and send the statement to a destination hostgroup. Matching digests with match_digest is usually preferable when you have a stable statement shape because digests are smaller and matching is faster.
For example, this rule sends one known SELECT shape from appuser to reader hostgroup 2:
Free tools Windows power users keep installed
One-click scans. No signup required.
INSERT INTO mysql_query_rules
(rule_id,active,username,match_digest,destination_hostgroup,apply)
VALUES (10,1,'appuser','^SELECT c FROM sbtest1 WHERE id=?',2,1);
LOAD MYSQL QUERY RULES TO RUNTIME;
SAVE MYSQL QUERY RULES TO DISK;apply=1 stops evaluation after this rule matches. That is useful when the routing decision is final, but dangerous on a broad rule. A broad early rule with a destination hostgroup or apply=1 can capture traffic that a later, more specific rule was supposed to handle.
Build rules from narrow to broad
- List statements that are proven safe to run on readers.
- Give each important pattern a distinct, ordered
rule_id. - Match the application username when different users need different routing.
- Prefer a digest pattern that identifies the intended statement without matching unrelated SQL.
- Use
apply=1only when no later rule should inspect a match. - Leave the writer default in place for unmatched statements and for operations whose consistency requirements are uncertain.
- Load the rules into runtime, save them to disk, then inspect the runtime table to confirm order and destination.
Do not begin with a catch-all rule that sends every SELECT to replicas. Such a rule can break read-your-own-write behavior, route session-dependent statements incorrectly, and prevent later rules from running.
Understand ProxySQL’s three configuration layers
ProxySQL separates configuration into three layers:
- Main tables: the editable configuration tables, such as
mysql_servers,mysql_users,mysql_query_rules, andglobal_variables. - Runtime tables: the configuration currently used by ProxySQL worker threads. These are visible through tables such as
runtime_mysql_serversandruntime_mysql_query_rules. - Disk configuration: the SQLite-backed state restored after a restart.
Use the matching load and save operations after editing:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems-- edit main tables first
LOAD MYSQL SERVERS TO RUNTIME;
LOAD MYSQL USERS TO RUNTIME;
LOAD MYSQL QUERY RULES TO RUNTIME;
LOAD MYSQL VARIABLES TO RUNTIME;
SAVE MYSQL SERVERS TO DISK;
SAVE MYSQL USERS TO DISK;
SAVE MYSQL QUERY RULES TO DISK;
SAVE MYSQL VARIABLES TO DISK;Loading activates a change now. Saving persists it. You normally need both. If a change is visible in a main table but not in its runtime_ counterpart, it is not active. If it is active but not saved, a restart can restore the previous disk version.
Verify routing before sending production traffic
Verification should cover backend state, rule order, connection pools, and observed query destinations. From the Admin interface, run:
SELECT * FROM runtime_mysql_servers;
SELECT * FROM runtime_mysql_query_rules ORDER BY rule_id;
SELECT hostgroup, SUM(sum_time), SUM(count_star)
FROM stats_mysql_query_digest
GROUP BY hostgroup;
SELECT * FROM stats_mysql_connection_pool;Use a controlled traffic test
- Connect a test client or staging application to the ProxySQL MySQL traffic listener, not port
6032. - Run a representative write using the application account and confirm that it reaches the writer hostgroup.
- Run a read that matches a deliberately narrow reader rule and compare its hostgroup in
stats_mysql_query_digest. - Run an unmatched statement and confirm that the user’s
default_hostgroupis used. - Inspect
stats_mysql_connection_poolfor backend connections, status, and pool behavior. - Correlate the result with monitor connect, ping, and read-only logs.
- In a controlled test environment, make a backend unavailable or introduce a known replication-lag condition and confirm that its status changes as designed before declaring failover behavior ready.
stats_mysql_query_digest aggregates query shapes and timing by hostgroup, while stats_mysql_connection_pool shows how ProxySQL is maintaining backend pools. Together with the runtime tables and monitor logs, they provide evidence of where traffic is going rather than relying on a successful client connection alone.
Troubleshoot common failures
Changes disappear after a restart
The edit was made in a main table and loaded, but not saved to the disk layer. Re-run the relevant SAVE MYSQL ... TO DISK command, then verify the corresponding runtime and disk state. Remember that servers, users, query rules, and variables are saved separately.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Traffic never reaches a newly added server
Check the row in mysql_servers for the expected hostname, port, hostgroup, and status. Confirm that the server is ONLINE, verify network reachability and monitor credentials, then run LOAD MYSQL SERVERS TO RUNTIME. Inspect runtime_mysql_servers rather than only the main table.
Reads continue going to the writer
Check the application user’s default_hostgroup, the active query rules and their order, and the replication monitor’s view of read_only. A read rule that does not match the actual digest falls back to the user’s default. A backend reported as a writer will remain in the writer hostgroup until its observed state changes.
A later query rule never matches
Inspect earlier rows in runtime_mysql_query_rules. A broad match with apply=1, or an earlier rule that already sets a destination hostgroup, can stop evaluation. Narrow the earlier expression, move the specific rule to a lower rule_id, or remove the premature apply behavior.
Backends repeatedly move offline
Read the monitor connect, ping, and read-only logs. Check the monitor username and password on every backend, firewall and routing rules, DNS resolution, MySQL listener binding, TLS requirements if enabled, and replication lag. Do not mask flapping by loosening routing rules before identifying whether the cause is authentication, reachability, server health, or an overly strict lag threshold.
Choose between one ProxySQL node and a redundant deployment
A single ProxySQL node is operationally simpler but remains a proxy failure domain. Adding another node can reduce that risk, yet applications then need a way to reach both nodes and the configuration must remain consistent. Select the architecture from the database topology and availability objective, not from the number of servers alone.
Quick Recap
| Decision axis | Single ProxySQL node | Clustered or redundant ProxySQL deployment |
|---|---|---|
| Failure-domain coverage | ProxySQL host failure can interrupt database access even when MySQL is healthy. | Can tolerate one proxy failure if clients or an upstream mechanism can reach another node. |
| Configuration synchronization | One Admin database is easier to operate and audit. | Requires a deliberate synchronization method and change ownership so rules do not diverge. |
| Health and failover behavior | One monitoring view controls routing. | Every proxy must observe compatible backend state and apply equivalent routing policy. |
| Read/write consistency | One rule set and pool view simplify diagnosis. | Consistency requirements remain; multiple proxies do not eliminate replica lag or read-after-write issues. |
| Connection capacity | Capacity is bounded by one proxy’s resources and limits. | Capacity can be distributed, subject to backend connection budgets and client distribution. |
| TLS exposure and access control | Fewer endpoints to secure and monitor. | More listener, certificate, and management endpoints require consistent hardening. |
| Observability | One set of runtime tables, pool statistics, and digests. | Metrics and logs must be collected and compared across nodes. |
| Operational complexity | Lower, appropriate for a small or non-critical installation. | Higher, justified when proxy availability and failure-domain coverage are requirements. |
Production readiness checklist
- Applications use the traffic listener, commonly
6033, while administrators use the restricted Admin interface at6032. - Every backend has the intended hostname, port, hostgroup, status, connection limit, and lag policy.
- The monitor account is separate from application users and has only the required privileges.
- Writer and reader hostgroups agree with the real replication topology and observed
read_onlyvalues. - Application users exist in both MySQL and ProxySQL, with least-privilege grants and a safe writer fallback.
- Rules are specific, ordered, loaded into runtime, and saved to disk.
- Runtime tables show the configuration that worker threads actually use.
- Monitor logs, connection-pool statistics, and query digests are retained or exported for diagnosis.
- A controlled test has demonstrated expected behavior for a failed backend and a lagging replica.
- Admin credentials, monitor secrets, and application passwords are no longer documentation examples.
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.
