Cucumi I completely understand you. I’ve always said that change won’t be comfortable, but in the end, it will be necessary. We have already identified and resolved many issues that were generating warnings and errors in PHP, but we still need to address metadata serialization.
This will be the most significant change, as it will allow us to reduce up to 25 database queries into a single one. However, we will leave this for last, as it requires careful consideration of multiple aspects beforehand. Nonetheless, the code has already been refactored to facilitate this implementation.
This is part of our process; the goal is to ensure that you can keep your current database. So far, the code refactoring has been highly beneficial, allowing us to identify and fix unnecessary loops and redundant code. Additionally, we have removed modules and comparative operations that no longer provided value.
That said, the key change will be metadata serialization. This process will not only optimize the overall system performance but also reduce database load, improving response speed and site scalability. With a more efficient storage structure, large volumes of data can be managed without compromising performance.
On the other hand, any website with a large database will always require server optimization. Improving the code alone is not enough; it is essential to fine-tune server configurations, optimize caching, use proper database indexing, and ensure that hosting resources are sufficient to handle traffic demand. Only with a comprehensive strategy can we guarantee an efficient and stable system in the long run.
