Bug Fix Repair Tables - Odd Overhead Size

[techieanalyst]

Noticed this not to long ago, seems a bit much but under Repair / Optimize Tables I noticed this

credits_transaction

10.50 MB

17.47 MB

66.00 MB

Overhead is 66MBytes, is this normal?

 

[Darkwaltz4]

how many rows do you have in your transaction table, and when was the last time you optimized? high answers to either (or both!) will cause that, and isnt an "issue" to fix.

 

[techieanalyst]

cant optimize the table states its an InnoDB

 

[techieanalyst]

Weird there are a few, must be sharing the same table

credits_transaction

10.50 MB

17.47 MB

66.00 MB

dbtech_vbarcade_data

16.0 KB

0

66.00 MB

dbtech_vbarcade_session

16.0 KB

0

66.00 MB

 

[Darkwaltz4]

the tables maintain a decent index to keep it running fast. is this causing any issues aside from alarm? again, i cant "fix" this without sacrificing the lookup speed, which is more desirable.

 

[techieanalyst]

You need to add one more catagory "Possible Issue" lol I would have selected that instead

Speed is desirable by far, but the alarm was how big is it going to get and how fast is it going to get there. My main concern was performance but your saying as is its better off, and I trust your word for it

 

[Darkwaltz4]

Did you run the new index query from one of the more recent threads (last few months)? If not, then PM me and I can switch the indexes for you and should have some minor improvement in size.