templating VS Spiral Framework

There are also some small template engines available like mustache or handlebars without big dependencies tree. I'm working on a templating abstraction to make this more easier to use any template engine you want so your controller dont need to care about it: https://github.com/schranz-templating/templating

It is supported via the Spiral View. The viewmanager by default will call Stempler you can test it out in the example spiral application running in examples/usages/spiral direcotory visiting /spiral-view will call the template here: https://github.com/schranz-templating/templating/blob/0.1/examples/usages/spiral/app/views/base.dark.php

From the same developers :

PHP framework : https://spiral.dev/

ORM library : https://cycle-orm.dev/

This SDK server is already available for RoadRunner 2.0+ and Spiral Framework users.

✅ Spiral (Twig, Blade, Latte, Plates, Smarty, Handlebars, Mustache, Spiral View)

To give you some hint, you mention few of our instruments - RoadRunner, Cycle ORM. Accidentally, theese instruments are also part of our main battle framework - Spiral (https://github.com/spiral/framework), which we use for all of our commercial projects for over 12 years so far.

Check https://github.com/spiral/framework - it would satisfy your perf requirements (roadrunner under the hood). We pushed it up to 250k on synthetic hello world, but in real world 20k are achievable without much hassle.

Yes, you are responsible for cleaning the memory after yourself. Most of modern frameworks can do it for you since they can control the state using DI. If you are looking for a more friendly way to manage memory take a look at https://github.com/spiral/framework It is Symfony like framework developed specifically for resident memory applications.