• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

I can increase the PHP limit my server to 3GB?

Jonatan442

Basic Pleskian
Hello!

My site database has 1.9 GB.

PHP limit my server is 512 MB.

This may be causing my site problems?

I can increase this limit to 3000 MB? I can cause some trouble for doing this?

The limits of my server:

CPU 4 Cores
RAM 14 GB
Disk Storage: 1000 GB
 
@Jonatan442

What I do not understand, is related to the following: a large database should not matter, if an application or client (in general) chunks up requests to the database.

It seems to be the case that you are making many requests to the database.

I am pretty sure that most of them are similar or identical.

Your problem would probably not existing and/or is very likely to be solved if

a) code (i.e. php scripts) treats parts of the database entries as "dynamic" (to be requested by clients/applications) and the remainder as "static" (not loaded, unless necessary).

For example, consider a web application, serving content from a database: not all the database data can be served in one (visible) page, some of the data does not have to be loaded.

OR

b) specific database data, that is requested frequently and for which the mysql command is similar/identical, is served via cache, preferably memory based cache (like Redis Cache)

For example, consider a web application, serving similar/identical content frequently from a database: one connection suffices to get the data into the memory based cache (read: only one or just small number of mysql connections) and the memory based cache serves the (similar/identical) content from memory (note: Redis can serve > 10K requests per second).

OR

c) the database is properly indexed, reducing the number of mysql connections to some extent and certainly decreasing the workload on the MySQL server.


In conclusion, there are many ways to enhance the performance of your site, but increasing memory limits is certainly not a good method.

In fact, allowing more memory will (on the one hand) not solve the problem of limited mysql connections and (on the other hand) give more "space" to bad code to make more use of resources, which essentially implies that the problem is aggravated.

I would strongly recommend to review the code and/or introduce caching mechanisms in the applications running on your site.

Hope the above helps and explains a little bit.

Regards......
 
Back
Top