Performance testing Thirybees on Orangepi 5, 8gb with M.2 ssd -

[Petter]

ab -n 10000 -c 100 -k https/XXXX.XX/index.php 2>&1 | grep "Requests per second\|Time per request\|Failed"
Failed requests:        0
Requests per second:    8402.12 [#/sec] (mean)
Time per request:       11.902 [ms] (mean)
Time per request:       0.119 [ms] (mean, across all concurrent requests)
root@orangepi5:/var/www/thirtybees#

8400 requests per second at 100 concurrent users with zero failures!

That's an absolutely remarkable result for an ~$80 ARM board. To put it in perspective:

• 8400 req/s — would handle massive traffic spikes
• 0.119ms per request across concurrent users
• Zero failed requests
• Pure nginx serving from memory cache, no PHP, no database

This Orange Pi 5 with NVMe + nginx fastcgi_cache could handle a serious production thirtybees store. Most small/medium e-commerce sites see maybe 10-50 req/s peak traffic.

Final stack summary:

• ✅ Nginx 1.29 with fastcgi_cache
• ✅ PHP 8.3-FPM (80 workers)
• ✅ MariaDB with 2GB buffer pool
• ✅ Valkey (Redis-compatible) for DB query cache
• ✅ Thirtybees page cache as fallback
• ✅ OPcache enabled

• noatime —  in fstab with commit=600 (batches writes every 600 seconds)
• zram swap — running with 3.9GB lzo-rle compressed swap
• zram /var/log — logs are in RAM (50MB), reducing disk writes

cat /etc/os-release
uname -a
PRETTY_NAME="Armbian 26.2.0-trunk.811 bookworm"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.armbian.com/"
SUPPORT_URL="https://forum.armbian.com"
BUG_REPORT_URL="https://www.armbian.com/bugs"
ARMBIAN_PRETTY_NAME="Armbian 26.2.0-trunk.811 bookworm"
Linux orangepi5 6.1.115-vendor-rk35xx #1 SMP Sat Apr 25 16:15:42 UTC 2026 aarch64 GNU/Linux
root@orangepi5:/var/www/thirtybees# 

 

Edited 17 hours ago by Petter
Updated with more info

[Petter]

orangepi5-thirtybees-setup.md

 

orangepi5-thirtybees-setup.md