Hi Steve,
Thank you for the pointer. I have looked into this approach but I'm on a shared hosting provider. I don't have the access or permissions to run a database optimization from an SSH.
I've also looked into running something similar from the MariaDB client, but none of the commands I have tried worked with the version of MariaDB I am on. It looks like optimizing per table is an option - but it requires the innodb_file_per_table to be set to on to recover lost space. Currently it is set to off. I don't have the super user privileges to set this to true on the shared database server.
I tried copying the data to a new table to see if I got any significant reductions - it went from 380mb to 365mb. It's not the sort of space recovery I was hoping for with so few rows in the table.
Are the figures we're discussing pretty much what is to be expected of the nf_users table, or is there another avenue I might be able to explore to help reduce the size of this table?
Thank you for the pointer. I have looked into this approach but I'm on a shared hosting provider. I don't have the access or permissions to run a database optimization from an SSH.
I've also looked into running something similar from the MariaDB client, but none of the commands I have tried worked with the version of MariaDB I am on. It looks like optimizing per table is an option - but it requires the innodb_file_per_table to be set to on to recover lost space. Currently it is set to off. I don't have the super user privileges to set this to true on the shared database server.
I tried copying the data to a new table to see if I got any significant reductions - it went from 380mb to 365mb. It's not the sort of space recovery I was hoping for with so few rows in the table.
Are the figures we're discussing pretty much what is to be expected of the nf_users table, or is there another avenue I might be able to explore to help reduce the size of this table?
Statistics: Posted by NewToPHPBoards — Sat May 04, 2024 7:16 am