Use MySQL workbench.
Add query to the editor, execute, check results.
Then, use the "Execution plan" feature to see how things are executing and look
for bad things (Cartesian products, stupid loops, etc...)
See also: Query stats.
Michael Munger, dCAP, MCPS, MCNPS, MBSS
High Powered Help,
Is there a way, perhaps with a script or a service, that one can check
MySQL code to see about making it more efficient? I maintain an open source
shopping cart written in Perl and it’s been awhile since the SQL has been
worked on, so I want to see if it could use some updating.
Dear MySQL Users,
MySQL Cluster is the distributed, shared-nothing variant of MySQL.
This storage engine provides:
- In-Memory storage - Real-time performance (with optional
checkpointing to disk)
- Transparent Auto-Sharding - Read & write scalability
- Active-Active/Multi-Master
Dear MySQL Users,
MySQL Cluster is the distributed, shared-nothing variant of MySQL.
This storage engine provides:
- In-Memory storage - Real-time performance (with optional
checkpointing to disk)
- Transparent Auto-Sharding - Read & write scalability
- Active-Active/Multi-Master
[This is part 3 of the announcement]
* JSON: When a JSON value consisted of a large sub-document
wrapped in many levels of JSON arrays, objects, or both,
serialization of the JSON value sometimes required an
excessive amount time to complete. (Bug #23031146)
*
[ This is part 2 of the announcement ]
Functionality Added or Changed
* InnoDB: By default, InnoDB reads uncommitted data when
calculating statistics. In the case of an uncommitted
transaction that deletes rows from a table, InnoDB
excludes records that are
