Free hosting is now upgraded to PHP 8.4

News and Announcements
1

As of last Monday, all free hosting servers have been upgraded to PHP 8.4.

A new PHP version is released every year, and free hosting was still on PHP 8.3, which was released in 2023. By now, almost all software has been updated to support PHP 8.4, and more and more software is starting to require it. So with this upgrade, free hosting remains a great place to host the latest and greatest of software.

PHP 8.4 comes with a number of changes to the language, including property hooks, asymmetric visibility and an updated DOM API. You can review the official announcement from PHP here: PHP: PHP 8.4 Release Announcement

And yes, PHP 8.5 exists too. However, it can take a long time for script developers to make their software compatible with new PHP versions, and for website owners to install those updates. That’s why we generally lag behind the official releases for a while, to make sure the upgrade doesn’t unnecessarily break websites.

6 Likes
3

A post was split to a new topic: Something went wrong

4

fyi

Copy-pasted content

Short answer: PHP 8.4 can feel heavier than 8.3 if certain extensions, JIT settings, or OPcache behaviors changed during the upgrade. You can usually fix the slowdown by tuning OPcache, adjusting JIT, checking extensions, and profiling bottlenecks.

-–

:gear: Practical ways to improve PHP 8.4 performance (English)

1. Optimize OPcache

PHP 8.4 relies more heavily on OPcache, and default values may not be ideal for your workload.

Increase memory and enable aggressive optimization:

`

opcache.enable=1

opcache.enable_cli=1

opcache.memory_consumption=256

opcache.internedstringsbuffer=32

opcache.maxacceleratedfiles=20000

opcache.validate_timestamps=0

opcache.revalidate_freq=0

`

Why it helps: Reduces repeated parsing and compilation overhead, especially on busy servers.

-–

2. Tune JIT settings

PHP 8.4’s JIT can slow down certain workloads (especially I/O‑bound or framework-heavy apps).

Try disabling or lowering JIT:

`

opcache.jit=off

`

or

`

opcache.jit=1205

`

Why it helps: JIT is beneficial for CPU-heavy loops, but can add overhead for typical web apps.

-–

3. Check extension compatibility

Some extensions (especially database drivers, XML, intl, or custom modules) may behave differently under 8.4.

Actions:

- Reinstall extensions with the correct ABI

- Update to the latest stable builds

- Remove unused extensions to reduce memory footprint

-–

4. Profile slow endpoints

Use tools like:

- Xdebug profiler

- Blackfire

- Tideways

Look for:

- Slow database queries

- Excessive autoloading

- Heavy middleware

- Repeated filesystem access

Why it helps: PHP upgrades often expose hidden bottlenecks that were previously masked.

-–

5. Check your framework’s compatibility

Laravel, Symfony, WordPress, and others may require:

- Updated cache drivers

- Updated composer packages

- Removal of deprecated features that cause fallback behavior

-–

6. Upgrade your composer dependencies

Run:

`

composer update

`

Many libraries ship PHP‑version‑specific optimizations.

-–

7. Review FPM settings

PHP-FPM defaults may not match your new memory usage under 8.4.

Tune:

- pm.max_children

- pm.max_requests

- pm.processidletimeout

Why it helps: PHP 8.4 may use slightly more memory per worker.

-–

:compass: What I recommend you try first

1. Disable JIT → measure

2. Increase OPcache memory → measure

3. Update composer packages

4. Profile slow endpoints

These four steps solve 80% of “PHP feels slower after upgrade” cases.

-–

If you want, I can generate a server‑specific optimization plan for your environment.

Would you like to focus on PHP-FPM tuning, OPcache optimization, or application profiling?

5

Please stop slinging AI slop here. It’s an answer to a question that nobody asks, and only serves to mislead and confuse.

It makes many assumptions about our software stack that are objectively wrong, and most recommendations involve configuration and options that don’t match how our system works, and are inaccessible to end users entirely.

I don’t know how you are directing it to. But regardless of whether this is directed to website owners or to us, it’s useless.

If there is a problem, just tell us what the problem is so we can investigate it properly. Maybe we’ll use AI during that process, because we have AI tools too. We don’t need you to act as a meat proxy.

The feeling I get from the reply is that the question involves a performance problem. If there is a performance problem, then tell us, and show what’s happening. Then we can look into what’s actually happening on our systems and look for a solution that actually works.

5 Likes
6
Copy-pasted content

Skip to main contentAccessibility help

AI Mode

All

Short videos

Videos

Forums

More

Upgrade

give better ways to improve php 8.4 performance

To improve PHP 8.4 performance, you should leverage the version’s new core engine optimizations while applying standard production-level tuning. Because core micro-benchmarks show that PHP 8.x versions perform similarly out of the box, real gains come from native feature utilization and environment configuration.

YouTube

·Tideways

+1

1. Leverage Native PHP 8.4 Performance Enhancements

PHP 8.4 introduces several features designed to bypass traditional execution overhead.

Tideways

+1

Use Native Array Array Functions Instead of Loops: Replace custom foreach or array_filter logic with the new native functions: array_find(), array_find_key(), array_any(), and array_all(). Because they are written natively in C, they run faster than userland PHP loop conditions.

YouTube

·The Codeholic

+1

Utilize sprintf Responsibly: PHP 8.4 optimizes sprintf calls that only use %s or %d formatters. The engine automatically compiles these down to string interpolation, entirely eliminating the function call overhead at runtime.

YouTube

·Tideways

Decline Heavy Initializations via Lazy Objects: If your framework creates heavy objects that aren’t always used during a lifecycle, migrate them to the new native LazyGhost or LazyProxy architecture. This defers memory allocation and initialization until a property is explicitly accessed.

YouTube

·Programming Fields

+1

Switch to \Dom\HTMLDocument: If parsing HTML5, avoid the legacy DOMDocument. The new spec-compliant classes handle modern web standards with highly optimized native parsing.

Medium

2. Fine-Tune OpCache & JIT

Bytecode caching is mandatory for high-performance production sites. Update your php.ini file with these production settings:

YouTube

·CodeLucky

ini

; Enable OpCache

opcache.enable = 1

opcache.enable_cli = 1

; Allocate sufficient memory (adjust based on app size)

opcache.memory_consumption = 256

opcache.max_accelerated_files = 10000

; CRITICAL FOR PRODUCTION: Turn off file timestamp checking

opcache.validate_timestamps = 0

opcache.revalidate_frequency = 0

; JIT Configuration

opcache.jit = tracing

opcache.jit_buffer_size = 64M

Use code with caution.

Note: Turn validate_timestamps off only in production, as PHP will no longer check if your script files have changed until you clear the cache or restart the PHP process.

YouTube

·CodeLucky

3. Move to Modern Server Runtimes

Traditional php-fpm setups work well, but modern application servers reduce application bootstrap overhead.

FrankenPHP: A modern PHP app server written in Go that supports a Worker Mode. In worker mode, your application is booted into memory once, and subsequent HTTP requests bypass the entire framework boot cycle, multiplying throughput.

Swoole / RoadRunner: If you are comfortable writing asynchronous or event-driven code, use these runtimes to handle non-blocking I/O operations and database connection persistence.

4. Optimize Database Connectivity

Database operations are typically the primary bottleneck in web applications.

Use Driver-Specific PDO Classes: PHP 8.4 adds driver-specific subclasses like PDOMySQL or PDOSQLite. Instantiating through PDO::connect() removes generic abstraction layers and enables cleaner IDE type-safety.

Avoid SELECT *: Query only the exact columns required to save database memory and reduce hydration overhead in PHP.

LinkedIn

·Mark Shust

+1

5. Profile Your Application

Generic tips only go so far; you must profile your specific architecture to find real memory leaks or algorithmic bottlenecks.

YouTube

·Tideways

+1

Use production profilers like Tideways or Blackfire to identify slow function calls.

Avoid leaving Xdebug enabled in production environments, as its debugging hooks severely impact response times.

Medium

+3

To give you specific code or server changes, let me know:

What framework (Laravel, Symfony, WordPress, or plain PHP) are you running?

What web server engine (Nginx, Apache, or FrankenPHP) hosts your current application?

AI responses may include mistakes. Learn more

YouTube

·

Tideways

Performance, Operations and Debugging Improvements in …

28 Aug 2025 — PHP 8.4 introduces an optimization for the `sprintf` function. When `sprintf` is used with only `%s` or `%d` modifiers, it now com…

1m

YouTube

·

CodeLucky

:rocket: PHP Performance Optimization: Beginner’s Guide to Faster …

31 May 2025 — Optimize PHP application speed by enabling OpCache, which stores compiled PHP bytecode in memory, eliminating the need to parse an…

24s

Tideways

What’s new in PHP 8.4 in terms of performance, debugging …

With PHP 8.4, ambiguous naming of closures in stack traces has been improved. debuggers and profilers such as Xdebug and Tideways …

Show all

Skip to previous prompt

Ask anything

AI Mode response is ready

Ask about

This should be better than the previous response because this response wasn’t written using AI

1 Like
7

It’s not better. You are just copy pasting an entire YouTube page and this makes your reply a total mess.

Even without all that it still falls into what Admin have said above:

Your last sentence also sounds like that you are the same person with emplant2000, but that’s not even a big issue now. You are answering Admin’s reply even though it’s directed to a supposedly different person:

Whatever. Please stop.

3 Likes
8

Agreed, that’s even worse.

Just stop copy-pasting crap here. It’s not helping anyone. It’s an answer to a question that nobody asked, and it’s for the most part wrong.

Or more specifically: the copy-pasted slop doesn’t seem factually wrong about PHP 8.4, but is completely misses that this is shared hosting, and most of those settings are not accessible to you and not yours to worry about. The only thing that people may need to do is update their website software, but if, what and how they need to update depends on the software used and “update caching libraries” and “run composer install” are wrong for a big majority of users.

If people want to read about what’s new in PHP 8.4 in terms of features or options or performance, they can read about it themselves in articles online, watch videos about it or ask their favorite AI.

4 Likes