Why These Little Tweaks Matter<\/strong><\/h3>\n\n\n\nPeople often focus on upgrading hosting when their site feels slow. That works sometimes; but not if PHP is choking because it\u2019s trying to run too many processes, or it\u2019s timing out too early.<\/p>\n\n\n\n
Think of PHP and FPM settings like the tuning knobs on an old amplifier. You can have the best hardware in the world, but if it\u2019s not adjusted right, the output just won\u2019t sound good.<\/p>\n\n\n\n
Part 1: PHP Settings That Actually Make a Difference<\/strong><\/h2>\n\n\n\nRunCloud\u2019s PHP settings area is pretty straightforward, but understanding what to tweak is what separates a smooth-running site from one that keeps freezing at random.<\/p>\n\n\n\n
1. max_execution_time -When PHP Gives Up<\/strong><\/h3>\n\n\n\nThis setting tells PHP when to stop waiting for a script to finish.
If you\u2019ve ever had an import hang forever or a backup quit halfway through, this is the reason.<\/p>\n\n\n\n
The default is 30 seconds<\/strong>, which is fine for lightweight sites. But if you\u2019re dealing with something heavier, like WooCommerce imports or image optimization tasks, bump it to 300 seconds<\/strong>.<\/p>\n\n\n\nThat said, don\u2019t use this as an excuse to let inefficient scripts run wild; it\u2019s there to help genuine heavy lifting, not to mask sloppy code.<\/p>\n\n\n\n
2. max_input_time – Time Spent Reading Data<\/strong><\/h3>\n\n\n\nThis controls how long PHP will spend reading incoming data (like form submissions or uploads).
If your site handles big uploads or massive forms, increasing it to 300 seconds<\/strong> saves you from annoying timeouts.<\/p>\n\n\n\nIf you\u2019re running something small, leave it alone – the default usually works fine.<\/p>\n\n\n\n
3. max_input_vars – How Many Fields PHP Can Handle<\/strong><\/h3>\n\n\n\nThis one\u2019s sneaky. Some CMS tools and plugins throw thousands of fields at PHP. If it\u2019s capped too low, PHP just\u2026 drops some of them.<\/p>\n\n\n\n
I usually start by increasing this from 1000<\/strong> to 3000 or 5000<\/strong>, depending on the app. But go slow – higher limits can eat into memory and slow things down if you\u2019re not careful.<\/p>\n\n\n\n4. memory_limit – The Hidden Bottleneck<\/strong><\/h3>\n\n\n\nIf you\u2019ve ever had a script crash without an obvious reason, check this first.
The memory limit sets how much RAM each PHP process can use.<\/p>\n\n\n\n
If it\u2019s too low, big scripts crash mid-process. Too high, and you\u2019ll starve the rest of your system.
For a 16 GB server, I\u2019ve found that giving PHP around 4\u20136 GB<\/strong> keeps things balanced.<\/p>\n\n\n\n5. post_max_size – How Big a POST Can Be<\/strong><\/h3>\n\n\n\nThis decides how much data PHP will accept in a single POST request. It\u2019s especially relevant if your site allows file uploads.<\/p>\n\n\n\n
If uploads are failing, the cause is often that this limit is smaller than your upload size.
For example, if you allow 100MB uploads, set post_max_size to at least 128MB<\/strong> to be safe.<\/p>\n\n\n\n6. upload_max_filesize – The File Upload Ceiling<\/strong><\/h3>\n\n\n\nThis one\u2019s directly tied to the setting above. It defines how large a single uploaded file can be.<\/p>\n\n\n\n
If users send big files – PDFs, videos, or image-heavy documents, make sure this value actually matches what your site allows. I\u2019ve seen sites where it\u2019s left at 8MB while the business tries to upload 60MB videos.<\/p>\n\n\n\n
And remember: PHP can\u2019t go higher than what your web server or operating system permits. Everything needs to match.<\/p>\n\n\n\n
7. session.gc_maxlifetime – How Long Users Stay Logged In<\/strong><\/h3>\n\n\n\nNothing annoys users faster than being logged out mid-task.<\/p>\n\n\n\n
This setting tells PHP how long a session can live before it\u2019s deleted. For e-commerce or admin dashboards, increase it so users don\u2019t lose carts or work.<\/p>\n\n\n\n
I often set it somewhere between 1 and 4 hours<\/strong>, depending on the app. It\u2019s not glamorous, but it\u2019s one of those small changes that make the user experience noticeably better.<\/p>\n\n\n\nPart 2: Getting PHP-FPM Right<\/strong><\/h2>\n\n\n\nOnce PHP is behaving, turn to PHP-FPM<\/a><\/strong> that\u2019s the piece that actually manages PHP workers and handles the traffic load.
Getting this right is the difference between a site that occasionally stutters<\/em> and one that stays rock solid when 200 people hit it at once.<\/p>\n\n\n\nRunCloud lets you adjust these settings in the dashboard, which makes testing changes less intimidating.<\/p>\n\n\n\n
FPM Modes Explained in Plain English<\/strong><\/h3>\n\n\n\nPHP-FPM can run in three modes, and choosing the right one matters more than people think:<\/p>\n\n\n\n
\n- On-Demand<\/strong> \u2013 Spawns workers only when requests come in. Perfect for low-traffic sites or staging environments.<\/li>\n\n\n\n
- Dynamic<\/strong> \u2013 Keeps a few workers ready, then adds or removes as traffic changes. I use this 90% of the time – it\u2019s flexible and reliable.<\/li>\n\n\n\n
- Static<\/strong> \u2013 Keeps a fixed number of workers running constantly. Great for high, steady traffic (like SaaS apps), but it eats memory.<\/li>\n<\/ul>\n\n\n\n
If you\u2019re unsure, start with Dynamic<\/strong>, then watch your graphs. RunCloud gives great insight into how workers scale during load.<\/p>\n\n\n\nImportant FPM Parameters You\u2019ll See<\/strong><\/h3>\n\n\n\n
RunCloud\u2019s PHP settings area is pretty straightforward, but understanding what to tweak is what separates a smooth-running site from one that keeps freezing at random.<\/p>\n\n\n\n
1. max_execution_time -When PHP Gives Up<\/strong><\/h3>\n\n\n\nThis setting tells PHP when to stop waiting for a script to finish.
If you\u2019ve ever had an import hang forever or a backup quit halfway through, this is the reason.<\/p>\n\n\n\n
The default is 30 seconds<\/strong>, which is fine for lightweight sites. But if you\u2019re dealing with something heavier, like WooCommerce imports or image optimization tasks, bump it to 300 seconds<\/strong>.<\/p>\n\n\n\nThat said, don\u2019t use this as an excuse to let inefficient scripts run wild; it\u2019s there to help genuine heavy lifting, not to mask sloppy code.<\/p>\n\n\n\n
2. max_input_time – Time Spent Reading Data<\/strong><\/h3>\n\n\n\nThis controls how long PHP will spend reading incoming data (like form submissions or uploads).
If your site handles big uploads or massive forms, increasing it to 300 seconds<\/strong> saves you from annoying timeouts.<\/p>\n\n\n\nIf you\u2019re running something small, leave it alone – the default usually works fine.<\/p>\n\n\n\n
3. max_input_vars – How Many Fields PHP Can Handle<\/strong><\/h3>\n\n\n\nThis one\u2019s sneaky. Some CMS tools and plugins throw thousands of fields at PHP. If it\u2019s capped too low, PHP just\u2026 drops some of them.<\/p>\n\n\n\n
I usually start by increasing this from 1000<\/strong> to 3000 or 5000<\/strong>, depending on the app. But go slow – higher limits can eat into memory and slow things down if you\u2019re not careful.<\/p>\n\n\n\n4. memory_limit – The Hidden Bottleneck<\/strong><\/h3>\n\n\n\nIf you\u2019ve ever had a script crash without an obvious reason, check this first.
The memory limit sets how much RAM each PHP process can use.<\/p>\n\n\n\n
If it\u2019s too low, big scripts crash mid-process. Too high, and you\u2019ll starve the rest of your system.
For a 16 GB server, I\u2019ve found that giving PHP around 4\u20136 GB<\/strong> keeps things balanced.<\/p>\n\n\n\n5. post_max_size – How Big a POST Can Be<\/strong><\/h3>\n\n\n\nThis decides how much data PHP will accept in a single POST request. It\u2019s especially relevant if your site allows file uploads.<\/p>\n\n\n\n
If uploads are failing, the cause is often that this limit is smaller than your upload size.
For example, if you allow 100MB uploads, set post_max_size to at least 128MB<\/strong> to be safe.<\/p>\n\n\n\n6. upload_max_filesize – The File Upload Ceiling<\/strong><\/h3>\n\n\n\nThis one\u2019s directly tied to the setting above. It defines how large a single uploaded file can be.<\/p>\n\n\n\n
If users send big files – PDFs, videos, or image-heavy documents, make sure this value actually matches what your site allows. I\u2019ve seen sites where it\u2019s left at 8MB while the business tries to upload 60MB videos.<\/p>\n\n\n\n
And remember: PHP can\u2019t go higher than what your web server or operating system permits. Everything needs to match.<\/p>\n\n\n\n
7. session.gc_maxlifetime – How Long Users Stay Logged In<\/strong><\/h3>\n\n\n\nNothing annoys users faster than being logged out mid-task.<\/p>\n\n\n\n
This setting tells PHP how long a session can live before it\u2019s deleted. For e-commerce or admin dashboards, increase it so users don\u2019t lose carts or work.<\/p>\n\n\n\n
I often set it somewhere between 1 and 4 hours<\/strong>, depending on the app. It\u2019s not glamorous, but it\u2019s one of those small changes that make the user experience noticeably better.<\/p>\n\n\n\nPart 2: Getting PHP-FPM Right<\/strong><\/h2>\n\n\n\nOnce PHP is behaving, turn to PHP-FPM<\/a><\/strong> that\u2019s the piece that actually manages PHP workers and handles the traffic load.
Getting this right is the difference between a site that occasionally stutters<\/em> and one that stays rock solid when 200 people hit it at once.<\/p>\n\n\n\nRunCloud lets you adjust these settings in the dashboard, which makes testing changes less intimidating.<\/p>\n\n\n\n
FPM Modes Explained in Plain English<\/strong><\/h3>\n\n\n\nPHP-FPM can run in three modes, and choosing the right one matters more than people think:<\/p>\n\n\n\n
\n- On-Demand<\/strong> \u2013 Spawns workers only when requests come in. Perfect for low-traffic sites or staging environments.<\/li>\n\n\n\n
- Dynamic<\/strong> \u2013 Keeps a few workers ready, then adds or removes as traffic changes. I use this 90% of the time – it\u2019s flexible and reliable.<\/li>\n\n\n\n
- Static<\/strong> \u2013 Keeps a fixed number of workers running constantly. Great for high, steady traffic (like SaaS apps), but it eats memory.<\/li>\n<\/ul>\n\n\n\n
If you\u2019re unsure, start with Dynamic<\/strong>, then watch your graphs. RunCloud gives great insight into how workers scale during load.<\/p>\n\n\n\nImportant FPM Parameters You\u2019ll See<\/strong><\/h3>\n\n\n\n
If you\u2019ve ever had an import hang forever or a backup quit halfway through, this is the reason.<\/p>\n\n\n\n
That said, don\u2019t use this as an excuse to let inefficient scripts run wild; it\u2019s there to help genuine heavy lifting, not to mask sloppy code.<\/p>\n\n\n\n
2. max_input_time – Time Spent Reading Data<\/strong><\/h3>\n\n\n\nThis controls how long PHP will spend reading incoming data (like form submissions or uploads).
If your site handles big uploads or massive forms, increasing it to 300 seconds<\/strong> saves you from annoying timeouts.<\/p>\n\n\n\nIf you\u2019re running something small, leave it alone – the default usually works fine.<\/p>\n\n\n\n
3. max_input_vars – How Many Fields PHP Can Handle<\/strong><\/h3>\n\n\n\nThis one\u2019s sneaky. Some CMS tools and plugins throw thousands of fields at PHP. If it\u2019s capped too low, PHP just\u2026 drops some of them.<\/p>\n\n\n\n
I usually start by increasing this from 1000<\/strong> to 3000 or 5000<\/strong>, depending on the app. But go slow – higher limits can eat into memory and slow things down if you\u2019re not careful.<\/p>\n\n\n\n4. memory_limit – The Hidden Bottleneck<\/strong><\/h3>\n\n\n\nIf you\u2019ve ever had a script crash without an obvious reason, check this first.
The memory limit sets how much RAM each PHP process can use.<\/p>\n\n\n\n
If it\u2019s too low, big scripts crash mid-process. Too high, and you\u2019ll starve the rest of your system.
For a 16 GB server, I\u2019ve found that giving PHP around 4\u20136 GB<\/strong> keeps things balanced.<\/p>\n\n\n\n5. post_max_size – How Big a POST Can Be<\/strong><\/h3>\n\n\n\nThis decides how much data PHP will accept in a single POST request. It\u2019s especially relevant if your site allows file uploads.<\/p>\n\n\n\n
If uploads are failing, the cause is often that this limit is smaller than your upload size.
For example, if you allow 100MB uploads, set post_max_size to at least 128MB<\/strong> to be safe.<\/p>\n\n\n\n6. upload_max_filesize – The File Upload Ceiling<\/strong><\/h3>\n\n\n\nThis one\u2019s directly tied to the setting above. It defines how large a single uploaded file can be.<\/p>\n\n\n\n
If users send big files – PDFs, videos, or image-heavy documents, make sure this value actually matches what your site allows. I\u2019ve seen sites where it\u2019s left at 8MB while the business tries to upload 60MB videos.<\/p>\n\n\n\n
And remember: PHP can\u2019t go higher than what your web server or operating system permits. Everything needs to match.<\/p>\n\n\n\n
7. session.gc_maxlifetime – How Long Users Stay Logged In<\/strong><\/h3>\n\n\n\nNothing annoys users faster than being logged out mid-task.<\/p>\n\n\n\n
This setting tells PHP how long a session can live before it\u2019s deleted. For e-commerce or admin dashboards, increase it so users don\u2019t lose carts or work.<\/p>\n\n\n\n
I often set it somewhere between 1 and 4 hours<\/strong>, depending on the app. It\u2019s not glamorous, but it\u2019s one of those small changes that make the user experience noticeably better.<\/p>\n\n\n\nPart 2: Getting PHP-FPM Right<\/strong><\/h2>\n\n\n\nOnce PHP is behaving, turn to PHP-FPM<\/a><\/strong> that\u2019s the piece that actually manages PHP workers and handles the traffic load.
Getting this right is the difference between a site that occasionally stutters<\/em> and one that stays rock solid when 200 people hit it at once.<\/p>\n\n\n\nRunCloud lets you adjust these settings in the dashboard, which makes testing changes less intimidating.<\/p>\n\n\n\n
FPM Modes Explained in Plain English<\/strong><\/h3>\n\n\n\nPHP-FPM can run in three modes, and choosing the right one matters more than people think:<\/p>\n\n\n\n
\n- On-Demand<\/strong> \u2013 Spawns workers only when requests come in. Perfect for low-traffic sites or staging environments.<\/li>\n\n\n\n
- Dynamic<\/strong> \u2013 Keeps a few workers ready, then adds or removes as traffic changes. I use this 90% of the time – it\u2019s flexible and reliable.<\/li>\n\n\n\n
- Static<\/strong> \u2013 Keeps a fixed number of workers running constantly. Great for high, steady traffic (like SaaS apps), but it eats memory.<\/li>\n<\/ul>\n\n\n\n
If you\u2019re unsure, start with Dynamic<\/strong>, then watch your graphs. RunCloud gives great insight into how workers scale during load.<\/p>\n\n\n\nImportant FPM Parameters You\u2019ll See<\/strong><\/h3>\n\n\n\n
If your site handles big uploads or massive forms, increasing it to 300 seconds<\/strong> saves you from annoying timeouts.<\/p>\n\n\n\n
If you\u2019re running something small, leave it alone – the default usually works fine.<\/p>\n\n\n\n
3. max_input_vars – How Many Fields PHP Can Handle<\/strong><\/h3>\n\n\n\nThis one\u2019s sneaky. Some CMS tools and plugins throw thousands of fields at PHP. If it\u2019s capped too low, PHP just\u2026 drops some of them.<\/p>\n\n\n\n
I usually start by increasing this from 1000<\/strong> to 3000 or 5000<\/strong>, depending on the app. But go slow – higher limits can eat into memory and slow things down if you\u2019re not careful.<\/p>\n\n\n\n4. memory_limit – The Hidden Bottleneck<\/strong><\/h3>\n\n\n\nIf you\u2019ve ever had a script crash without an obvious reason, check this first.
The memory limit sets how much RAM each PHP process can use.<\/p>\n\n\n\n
If it\u2019s too low, big scripts crash mid-process. Too high, and you\u2019ll starve the rest of your system.
For a 16 GB server, I\u2019ve found that giving PHP around 4\u20136 GB<\/strong> keeps things balanced.<\/p>\n\n\n\n5. post_max_size – How Big a POST Can Be<\/strong><\/h3>\n\n\n\nThis decides how much data PHP will accept in a single POST request. It\u2019s especially relevant if your site allows file uploads.<\/p>\n\n\n\n
If uploads are failing, the cause is often that this limit is smaller than your upload size.
For example, if you allow 100MB uploads, set post_max_size to at least 128MB<\/strong> to be safe.<\/p>\n\n\n\n6. upload_max_filesize – The File Upload Ceiling<\/strong><\/h3>\n\n\n\nThis one\u2019s directly tied to the setting above. It defines how large a single uploaded file can be.<\/p>\n\n\n\n
If users send big files – PDFs, videos, or image-heavy documents, make sure this value actually matches what your site allows. I\u2019ve seen sites where it\u2019s left at 8MB while the business tries to upload 60MB videos.<\/p>\n\n\n\n
And remember: PHP can\u2019t go higher than what your web server or operating system permits. Everything needs to match.<\/p>\n\n\n\n
7. session.gc_maxlifetime – How Long Users Stay Logged In<\/strong><\/h3>\n\n\n\nNothing annoys users faster than being logged out mid-task.<\/p>\n\n\n\n
This setting tells PHP how long a session can live before it\u2019s deleted. For e-commerce or admin dashboards, increase it so users don\u2019t lose carts or work.<\/p>\n\n\n\n
I often set it somewhere between 1 and 4 hours<\/strong>, depending on the app. It\u2019s not glamorous, but it\u2019s one of those small changes that make the user experience noticeably better.<\/p>\n\n\n\nPart 2: Getting PHP-FPM Right<\/strong><\/h2>\n\n\n\nOnce PHP is behaving, turn to PHP-FPM<\/a><\/strong> that\u2019s the piece that actually manages PHP workers and handles the traffic load.
Getting this right is the difference between a site that occasionally stutters<\/em> and one that stays rock solid when 200 people hit it at once.<\/p>\n\n\n\nRunCloud lets you adjust these settings in the dashboard, which makes testing changes less intimidating.<\/p>\n\n\n\n
FPM Modes Explained in Plain English<\/strong><\/h3>\n\n\n\nPHP-FPM can run in three modes, and choosing the right one matters more than people think:<\/p>\n\n\n\n
\n- On-Demand<\/strong> \u2013 Spawns workers only when requests come in. Perfect for low-traffic sites or staging environments.<\/li>\n\n\n\n
- Dynamic<\/strong> \u2013 Keeps a few workers ready, then adds or removes as traffic changes. I use this 90% of the time – it\u2019s flexible and reliable.<\/li>\n\n\n\n
- Static<\/strong> \u2013 Keeps a fixed number of workers running constantly. Great for high, steady traffic (like SaaS apps), but it eats memory.<\/li>\n<\/ul>\n\n\n\n
If you\u2019re unsure, start with Dynamic<\/strong>, then watch your graphs. RunCloud gives great insight into how workers scale during load.<\/p>\n\n\n\nImportant FPM Parameters You\u2019ll See<\/strong><\/h3>\n\n\n\n
4. memory_limit – The Hidden Bottleneck<\/strong><\/h3>\n\n\n\nIf you\u2019ve ever had a script crash without an obvious reason, check this first.
The memory limit sets how much RAM each PHP process can use.<\/p>\n\n\n\n
If it\u2019s too low, big scripts crash mid-process. Too high, and you\u2019ll starve the rest of your system.
For a 16 GB server, I\u2019ve found that giving PHP around 4\u20136 GB<\/strong> keeps things balanced.<\/p>\n\n\n\n5. post_max_size – How Big a POST Can Be<\/strong><\/h3>\n\n\n\nThis decides how much data PHP will accept in a single POST request. It\u2019s especially relevant if your site allows file uploads.<\/p>\n\n\n\n
If uploads are failing, the cause is often that this limit is smaller than your upload size.
For example, if you allow 100MB uploads, set post_max_size to at least 128MB<\/strong> to be safe.<\/p>\n\n\n\n6. upload_max_filesize – The File Upload Ceiling<\/strong><\/h3>\n\n\n\nThis one\u2019s directly tied to the setting above. It defines how large a single uploaded file can be.<\/p>\n\n\n\n
If users send big files – PDFs, videos, or image-heavy documents, make sure this value actually matches what your site allows. I\u2019ve seen sites where it\u2019s left at 8MB while the business tries to upload 60MB videos.<\/p>\n\n\n\n
And remember: PHP can\u2019t go higher than what your web server or operating system permits. Everything needs to match.<\/p>\n\n\n\n
7. session.gc_maxlifetime – How Long Users Stay Logged In<\/strong><\/h3>\n\n\n\nNothing annoys users faster than being logged out mid-task.<\/p>\n\n\n\n
This setting tells PHP how long a session can live before it\u2019s deleted. For e-commerce or admin dashboards, increase it so users don\u2019t lose carts or work.<\/p>\n\n\n\n
I often set it somewhere between 1 and 4 hours<\/strong>, depending on the app. It\u2019s not glamorous, but it\u2019s one of those small changes that make the user experience noticeably better.<\/p>\n\n\n\nPart 2: Getting PHP-FPM Right<\/strong><\/h2>\n\n\n\nOnce PHP is behaving, turn to PHP-FPM<\/a><\/strong> that\u2019s the piece that actually manages PHP workers and handles the traffic load.
Getting this right is the difference between a site that occasionally stutters<\/em> and one that stays rock solid when 200 people hit it at once.<\/p>\n\n\n\nRunCloud lets you adjust these settings in the dashboard, which makes testing changes less intimidating.<\/p>\n\n\n\n
FPM Modes Explained in Plain English<\/strong><\/h3>\n\n\n\nPHP-FPM can run in three modes, and choosing the right one matters more than people think:<\/p>\n\n\n\n
\n- On-Demand<\/strong> \u2013 Spawns workers only when requests come in. Perfect for low-traffic sites or staging environments.<\/li>\n\n\n\n
- Dynamic<\/strong> \u2013 Keeps a few workers ready, then adds or removes as traffic changes. I use this 90% of the time – it\u2019s flexible and reliable.<\/li>\n\n\n\n
- Static<\/strong> \u2013 Keeps a fixed number of workers running constantly. Great for high, steady traffic (like SaaS apps), but it eats memory.<\/li>\n<\/ul>\n\n\n\n
If you\u2019re unsure, start with Dynamic<\/strong>, then watch your graphs. RunCloud gives great insight into how workers scale during load.<\/p>\n\n\n\nImportant FPM Parameters You\u2019ll See<\/strong><\/h3>\n\n\n\n
The memory limit sets how much RAM each PHP process can use.<\/p>\n\n\n\n
For a 16 GB server, I\u2019ve found that giving PHP around 4\u20136 GB<\/strong> keeps things balanced.<\/p>\n\n\n\n
5. post_max_size – How Big a POST Can Be<\/strong><\/h3>\n\n\n\nThis decides how much data PHP will accept in a single POST request. It\u2019s especially relevant if your site allows file uploads.<\/p>\n\n\n\n
If uploads are failing, the cause is often that this limit is smaller than your upload size.
For example, if you allow 100MB uploads, set post_max_size to at least 128MB<\/strong> to be safe.<\/p>\n\n\n\n6. upload_max_filesize – The File Upload Ceiling<\/strong><\/h3>\n\n\n\nThis one\u2019s directly tied to the setting above. It defines how large a single uploaded file can be.<\/p>\n\n\n\n
If users send big files – PDFs, videos, or image-heavy documents, make sure this value actually matches what your site allows. I\u2019ve seen sites where it\u2019s left at 8MB while the business tries to upload 60MB videos.<\/p>\n\n\n\n
And remember: PHP can\u2019t go higher than what your web server or operating system permits. Everything needs to match.<\/p>\n\n\n\n
7. session.gc_maxlifetime – How Long Users Stay Logged In<\/strong><\/h3>\n\n\n\nNothing annoys users faster than being logged out mid-task.<\/p>\n\n\n\n
This setting tells PHP how long a session can live before it\u2019s deleted. For e-commerce or admin dashboards, increase it so users don\u2019t lose carts or work.<\/p>\n\n\n\n
I often set it somewhere between 1 and 4 hours<\/strong>, depending on the app. It\u2019s not glamorous, but it\u2019s one of those small changes that make the user experience noticeably better.<\/p>\n\n\n\nPart 2: Getting PHP-FPM Right<\/strong><\/h2>\n\n\n\nOnce PHP is behaving, turn to PHP-FPM<\/a><\/strong> that\u2019s the piece that actually manages PHP workers and handles the traffic load.
Getting this right is the difference between a site that occasionally stutters<\/em> and one that stays rock solid when 200 people hit it at once.<\/p>\n\n\n\nRunCloud lets you adjust these settings in the dashboard, which makes testing changes less intimidating.<\/p>\n\n\n\n
FPM Modes Explained in Plain English<\/strong><\/h3>\n\n\n\nPHP-FPM can run in three modes, and choosing the right one matters more than people think:<\/p>\n\n\n\n
\n- On-Demand<\/strong> \u2013 Spawns workers only when requests come in. Perfect for low-traffic sites or staging environments.<\/li>\n\n\n\n
- Dynamic<\/strong> \u2013 Keeps a few workers ready, then adds or removes as traffic changes. I use this 90% of the time – it\u2019s flexible and reliable.<\/li>\n\n\n\n
- Static<\/strong> \u2013 Keeps a fixed number of workers running constantly. Great for high, steady traffic (like SaaS apps), but it eats memory.<\/li>\n<\/ul>\n\n\n\n
If you\u2019re unsure, start with Dynamic<\/strong>, then watch your graphs. RunCloud gives great insight into how workers scale during load.<\/p>\n\n\n\nImportant FPM Parameters You\u2019ll See<\/strong><\/h3>\n\n\n\n
For example, if you allow 100MB uploads, set post_max_size to at least 128MB<\/strong> to be safe.<\/p>\n\n\n\n
6. upload_max_filesize – The File Upload Ceiling<\/strong><\/h3>\n\n\n\nThis one\u2019s directly tied to the setting above. It defines how large a single uploaded file can be.<\/p>\n\n\n\n
If users send big files – PDFs, videos, or image-heavy documents, make sure this value actually matches what your site allows. I\u2019ve seen sites where it\u2019s left at 8MB while the business tries to upload 60MB videos.<\/p>\n\n\n\n
And remember: PHP can\u2019t go higher than what your web server or operating system permits. Everything needs to match.<\/p>\n\n\n\n
7. session.gc_maxlifetime – How Long Users Stay Logged In<\/strong><\/h3>\n\n\n\nNothing annoys users faster than being logged out mid-task.<\/p>\n\n\n\n
This setting tells PHP how long a session can live before it\u2019s deleted. For e-commerce or admin dashboards, increase it so users don\u2019t lose carts or work.<\/p>\n\n\n\n
I often set it somewhere between 1 and 4 hours<\/strong>, depending on the app. It\u2019s not glamorous, but it\u2019s one of those small changes that make the user experience noticeably better.<\/p>\n\n\n\nPart 2: Getting PHP-FPM Right<\/strong><\/h2>\n\n\n\nOnce PHP is behaving, turn to PHP-FPM<\/a><\/strong> that\u2019s the piece that actually manages PHP workers and handles the traffic load.
Getting this right is the difference between a site that occasionally stutters<\/em> and one that stays rock solid when 200 people hit it at once.<\/p>\n\n\n\nRunCloud lets you adjust these settings in the dashboard, which makes testing changes less intimidating.<\/p>\n\n\n\n
FPM Modes Explained in Plain English<\/strong><\/h3>\n\n\n\nPHP-FPM can run in three modes, and choosing the right one matters more than people think:<\/p>\n\n\n\n
\n- On-Demand<\/strong> \u2013 Spawns workers only when requests come in. Perfect for low-traffic sites or staging environments.<\/li>\n\n\n\n
- Dynamic<\/strong> \u2013 Keeps a few workers ready, then adds or removes as traffic changes. I use this 90% of the time – it\u2019s flexible and reliable.<\/li>\n\n\n\n
- Static<\/strong> \u2013 Keeps a fixed number of workers running constantly. Great for high, steady traffic (like SaaS apps), but it eats memory.<\/li>\n<\/ul>\n\n\n\n
If you\u2019re unsure, start with Dynamic<\/strong>, then watch your graphs. RunCloud gives great insight into how workers scale during load.<\/p>\n\n\n\nImportant FPM Parameters You\u2019ll See<\/strong><\/h3>\n\n\n\n
Nothing annoys users faster than being logged out mid-task.<\/p>\n\n\n\n
This setting tells PHP how long a session can live before it\u2019s deleted. For e-commerce or admin dashboards, increase it so users don\u2019t lose carts or work.<\/p>\n\n\n\n
I often set it somewhere between 1 and 4 hours<\/strong>, depending on the app. It\u2019s not glamorous, but it\u2019s one of those small changes that make the user experience noticeably better.<\/p>\n\n\n\n Once PHP is behaving, turn to PHP-FPM<\/a><\/strong> that\u2019s the piece that actually manages PHP workers and handles the traffic load. RunCloud lets you adjust these settings in the dashboard, which makes testing changes less intimidating.<\/p>\n\n\n\n PHP-FPM can run in three modes, and choosing the right one matters more than people think:<\/p>\n\n\n\n If you\u2019re unsure, start with Dynamic<\/strong>, then watch your graphs. RunCloud gives great insight into how workers scale during load.<\/p>\n\n\n\nPart 2: Getting PHP-FPM Right<\/strong><\/h2>\n\n\n\n
Getting this right is the difference between a site that occasionally stutters<\/em> and one that stays rock solid when 200 people hit it at once.<\/p>\n\n\n\nFPM Modes Explained in Plain English<\/strong><\/h3>\n\n\n\n
\n
Important FPM Parameters You\u2019ll See<\/strong><\/h3>\n\n\n\n
![\"Contact](\"https:\/\/no-cache.hubspot.com\/cta\/default\/2725694\/3350a795-db50-482f-9911-301930d1b1be.png\")
<\/a><\/span>