[Benchmark php frameworks]. Part 3. Phalcon.

Well, I got to benchmark the first framework according to my plan. ( More info about plan in the first part )

Some information about server for tests

After several attempts the server settings on the option:

Centos 7.2 + vestacp + apache2.4 + php 7.0.20 + mariadb 5.5.52 (I think later to install mariadb 10.1. What will you advise?)

2 X86 64bit Cores 2GB memory (https://www.scaleway.com/ Virtual SSD Cloud Servers / Starter )

Some information about framework.

Site: https://phalconphp.com/ru/

It positions itself as the fastest framework. Supplied as C-extension. It is loaded into memory with one file and used by all applications. More details on the site.

Let's see benchmark.

Just to remind about the structure ( Full description here )

• /phalcon-authors - lists of authors with posts counts.
• /phalcon-categories - list of categories with counts of posts in every one.
• /phalcon-posts - all posts with information about types, authors and categories.
• /phalcon-index - simple "hello world" for comparison

For my benchmark I took this code and made some modifications. All code committed to Github.

framework	requests per second	relative	peak memory	relative
phalcon-index	303.86	4,340.9	0.44	1.0
phalcon-authors	31.66	452.3	0.56	1.3
phalcon-categories	16.84	240.6	0.57	1.3
phalcon-posts	0.07	1.0	3.60	8.2

In general, as expected - the more connections between the tables - the worse the result.

The application code can be viewed at github https://github.com/semasping/php_frameworks_for_tests

There are already Laravel app code committed too, But test will be in next article.

Now the questions appear:

• How will laravel behave?
• How many requests per second will he give out on the most complicated version when displaying information about posts?
• Will laravel be worse then phalcon?

Please write your opinion in comments

Work on translation is already in the process - the article is coming soon.