MeMaBlue Posted December 28, 2016 Share Posted December 28, 2016 Hello, new database size is 15gb whereas the vbulletin db size was 3gb it seems the difference is due to the existence of full text indexes files for some of the tables we're using the innodb mysql engine for the new database is there any way we can claim back the disk used for the full text indices ? any tips? Link to comment Share on other sites More sharing options...
Jirinex Posted January 17, 2017 Share Posted January 17, 2017 No tips for reducing indexes, but do you have any tables starting with orig_ in the database? Link to comment Share on other sites More sharing options...
ASTRAPI Posted January 17, 2017 Share Posted January 17, 2017 Innodb uses about 3x more space.... Link to comment Share on other sites More sharing options...
marklcfc Posted January 17, 2017 Share Posted January 17, 2017 4 hours ago, ASTRAPI said: Innodb uses about 3x more space.... So if i change from myisam to innodb is my database going to go from 5gb to 15gb? Link to comment Share on other sites More sharing options...
ASTRAPI Posted January 17, 2017 Share Posted January 17, 2017 Yes it should be around 12-14 GB.... But Innodb have many advantages compared to myisam and if you have the space and a few extrra free ram is recommended to do :-) Link to comment Share on other sites More sharing options...
MeMaBlue Posted January 17, 2017 Author Share Posted January 17, 2017 4 hours ago, marklcfc said: So if i change from myisam to innodb is my database going to go from 5gb to 15gb? Yes this is true. It creates a problem when gou migrate and have all the backups and suddenly no space because you never expected it. I posted a ticket for it and researched it, nothing can be done. Link to comment Share on other sites More sharing options...
ASTRAPI Posted January 17, 2017 Share Posted January 17, 2017 Quote It creates a problem when gou migrate and have all the backups and suddenly no space because you never expected it. You should know how big is your database before you transfer to another server and get a server with enough disk space for it Quote I posted a ticket for it and researched it, nothing can be done. That's how it works and that's normal.There is nothing broken to get a fix.... Whether the trade-off between storage use and the features offered by InnoDB (crash-safety, transactions, and foreign keys) favours InnoDB is something you will have to decide on. Link to comment Share on other sites More sharing options...
MeMaBlue Posted January 23, 2017 Author Share Posted January 23, 2017 @ASTRAPI in our case, we had little margin of time, and had to go from vbulletin 3.8, to IPB 3.4 then to UTF8 then Upgrade from IPB 3.4 to IPB 4.1 imagine if you have a 80 gb disk and a 5 gb database, you might think it will be enough, but then ,some of these stages /backup / step is tripled in size ;-) i am not talking at all about the trade-off. just about the planning beforehead and knowing WHY your database is tripling, my IT didnt know and we lost a lot of time trying to figure out if something was wrong. (something is/might be wrong = you dont go ahead with the next step of the procedure......!!!!) So i think it would be good if the next somebody tries that, he knows what to expect - no time lost, no worries, just extra GB. Link to comment Share on other sites More sharing options...
ASTRAPI Posted January 23, 2017 Share Posted January 23, 2017 For me it sounds that something old/not needed anymore left there ? Don't know but you may open a support ticket so IPB support will check it. It is normal to get around triple size only if you was using MyISAM and you convert the tables to InnoDB ..... Link to comment Share on other sites More sharing options...
MeMaBlue Posted January 23, 2017 Author Share Posted January 23, 2017 we checked it , yes we were probably using that. i am not IT as I said, but these stages i am describing , did that effect, we opened a ticket , that was the cause, nothing can be done, just knowing in advance would be nice. Link to comment Share on other sites More sharing options...
.thumb.png.72c24494603afd7a572d55d4a71e4af2.png)
Recommended Posts
Archived
This topic is now archived and is closed to further replies.