 |
 |
 |
 |
Registered: 03/13/07
Posts: 28
|
|
|
 |
 |
 |
 |
|
 |
 |
 |
 |
#179858 - 03/02/07 03:20 AM
Re: Huge Cached Permission Table Overhead
[Re: Gizmo]
|
Carpal Tunnel
 
Registered: 07/04/06
Posts: 4044
Loc: Liverpool : England : UK
|
phpmyadmin V 2.8.2.4 Go to your Database Select >> Structure Scroll to the bottom Check tables having overhead (Click on this - it does nothing until you change the default.) Default = : With Selected Just change the default too "Optermize Table" And it does it all. NOTE : I'm not in a position to say if thats the right way or the wrong way, but ive just cleared a load of overhead. Using the above method. And as Gizmo points out would be a good idea before a back up too. Cheers Gizmo for the expination, makes sense now 
Edited by Mark S (03/02/07 03:25 AM) Edit Reason: added click on
_________________________
Version v7.2.2 < Threads satisfaction status People who inspire me Rick Gizmo Ian David jgeoff ntdoc To answer the question you must first give a question.
|
|
Top
|
|
|
|
|
 |
 |
 |
 |
 |
 |
 |
 |
#179862 - 03/02/07 03:33 AM
Re: Huge Cached Permission Table Overhead
[Re: Gizmo]
|
 
Registered: 06/04/06
Posts: 12006
Loc: Portland, OR; USA
|
BTW, heres a small chart to show the differance of using a script and using the command line.
Using a script: 1. Your browser, connects to the webserver. 2. The webserver connects to the MySQL server.
The problem here is that any requests to MySQL have to go through the webserver, and the webserver has a "maximum execution time" variable, once you go over this threshold, the server times out your request.
When the server is preforming critical tasks like optimizing or repairing tables, it locks those tables so that no new data can be written to them to avoid loss of data or possible curruption.
Using MySQL via command line: You access MySQL directly, there is no maximum execution timeframe, as the webserver is not involved. As no webserver is involved, there will be no additional resource usage through the webserver.
Please note though, that I would highly recommend that you optimize your database before backing it up; theres no sense in backing something up when it could be much smaller and "optimized". :nod: lol
|
|
Top
|
|
|
|
|
 |
 |
 |
 |
|
|