Conversation
supportHi ! Is it normal to have a database like “wpftsi_vectors” who got a size of 1,2Go ?? I don’t think its really normal and would like to know how to manage that 🙂 Thanks !
Hi @josselynj The size of the index tables could be large, because they store both data (in compressed form) and MySQL index (to find records pretty fast). However, this size depends on amount of data and texts in your WordPress website, for sure. It’s okay for MySQL, since it works with even bigger tables with no problem and integrated index allows to do that pretty fast. Could you explain why it’s not okay for you?
Hi, because we’ve have a warning for our hosting provider : “An important matter requires your prompt attention. Our system has detected the presence of large databases that may impact the performance of our shared hosting environment. To ensure smooth operation, please review the details below and reduce the usage accordingly. Each database should be less than 1GB in total size and individual database tables should contain less than 1,000,000 records.” So i trust them in the fact its not really normal to have huge databases like that. It’s sad because i would go to pro version but with this problem i won’t go further :/
Yes, I understand you. Shared hosting owners are trying to sell one physical server to thousands of clients at the same time; this is beneficial from a business point of view, but for this, all the inhabitants of this anthill must be small, quiet and inconspicuous. Therefore, sites on such hosting are subject to strict requirements regarding CPU load (usually questions arise when you spend more than 1% of CPU), the number and size of tables in the database, and so on. If you haven’t encountered these limitations yet, you will soon as your site grows. It’s your right to choose the type of hosting, but if your site has already become large and you can afford a small VPS server with no restrictions, then I would recommend looking in this direction. They are very inexpensive this day. Unfortunately, I cannot recommend to you other analogs of WPFTS that would perform fast searches through indexing and that would not use large index tables. This is the key thing, a quick search requires an index. And the index sometimes X times large than the source data. You can also consider some solutions that store the search index on a separate dedicated server (Elastic Search cloud), but in this case you will also have to pay for an additional service plus upload your data to third-party servers, which is not always convenient. If you have any questions, I’m ready to answer them.
Hi @josselynj The size of the index tables could be large, because they store both data (in compressed form) and MySQL index (to find records pretty fast). However, this size depends on amount of data and texts in your WordPress website, for sure. It’s okay for MySQL, since it works with even bigger tables with no problem and integrated index allows to do that pretty fast. Could you explain why it’s not okay for you?
Hi, because we’ve have a warning for our hosting provider : “An important matter requires your prompt attention. Our system has detected the presence of large databases that may impact the performance of our shared hosting environment. To ensure smooth operation, please review the details below and reduce the usage accordingly. Each database should be less than 1GB in total size and individual database tables should contain less than 1,000,000 records.” So i trust them in the fact its not really normal to have huge databases like that. It’s sad because i would go to pro version but with this problem i won’t go further :/
Yes, I understand you. Shared hosting owners are trying to sell one physical server to thousands of clients at the same time; this is beneficial from a business point of view, but for this, all the inhabitants of this anthill must be small, quiet and inconspicuous. Therefore, sites on such hosting are subject to strict requirements regarding CPU load (usually questions arise when you spend more than 1% of CPU), the number and size of tables in the database, and so on. If you haven’t encountered these limitations yet, you will soon as your site grows. It’s your right to choose the type of hosting, but if your site has already become large and you can afford a small VPS server with no restrictions, then I would recommend looking in this direction. They are very inexpensive this day. Unfortunately, I cannot recommend to you other analogs of WPFTS that would perform fast searches through indexing and that would not use large index tables. This is the key thing, a quick search requires an index. And the index sometimes X times large than the source data. You can also consider some solutions that store the search index on a separate dedicated server (Elastic Search cloud), but in this case you will also have to pay for an additional service plus upload your data to third-party servers, which is not always convenient. If you have any questions, I’m ready to answer them.