Skip to the products
LCPanelLicence Center Panel

Performance, the profiler and load testing

The caches and queues built in, the request profiler header, OPcache and PHP settings, the load-test tool and the 2.0.0 figures.

Reference Updated 6 Nov 2026 33 / 36

1. What the product does by itself

Caches for what repeats (home sections, category and extension counts, currency rates, trending searches, suggestions) in data/cache (or Redis when the host has it: AD_CACHE = 'redis' in config.php), pagination on every list, images resized and re-encoded at upload (WebP when the browser accepts it), mail and webhooks sent from the job queue so a page never waits for a mail server, counters kept on the rows and repaired nightly, the search on indexed columns with a relevance expression, API answers that browsers and proxies may cache, the sitemap built on disk by the cron.

2. The profiler

Switch Show error details to staff (debug) on under Settings -> Security, open any page with ?__prof=1 and read the response header X-AD-Profile: the number of queries, the database time, the whole time and the memory of that request; X-AD-Slow lists statements that took over 50 ms. Switch debug off again afterwards. A page whose query count grows with the amount of data (not with the page length) is the one to report.

3. OPcache and PHP settings

Without OPcache every request compiles the product again (about 70 ms); with it a page costs only its own work, typically 10 to 50 ms. The Health check shows whether OPcache is on; on cPanel it is a tick under Select PHP Version -> Options. memory_limit 256M and an upload size of 16M or more are the other two settings worth setting.

4. Load testing

The dev kit ships loadtest.php (php loadtest.php --base=https://your-site --c=10 --n=300): it fires a mix of the pages visitors hit most (home, search, a listing, a category, an extension, auctions, sellers, the API, the sitemap, the valuation and membership pages) with the given concurrency, warms the caches first, and prints requests per second, the p50 / p95 / max latency, errors and status codes, and per page the average queries and database time (from the profiler header when the site sends it). Run it against a staging copy before launch and after large imports; expect a healthy host with OPcache to answer the home page in well under 100 ms and to scale with its PHP workers.

The 2.0.0 figures on the development server (single-threaded, no OPcache, 100 demo listings): home 31 queries / 23 ms in the database / 50 ms in all, search 26 / 12 / 39, listing page 26 / 12 / 40, API search 8 / 8 / 15; 8.4 requests per second at concurrency 8 because that server answers one request at a time. Production numbers come from your own run.

Was this helpful?
Share this chapter