Measured benchmark · PostgreSQL vs PostgreSQL · POSMall Core

POSMall Core PostgreSQL vs Aimeos PostgreSQL Benchmark

POSMall Core beat the selected Aimeos PostgreSQL reference in both measured paths at all seven catalog sizes from 1,000 through 300,000 products. The table below is the primary public evidence.

Final internal Homestead benchmark checkpoint · Updated 2026-08-28

Final PostgreSQL-vs-PostgreSQL result table

Lower milliseconds are better. POSMall Core won 7 of 7 catalog sizes and 14 of 14 measured path comparisons in this same-environment internal synthetic benchmark.

Internal Homestead synthetic benchmark. Final checkpoint: posmall-aimeos-5way-current-checkpoint-20260610-024820.
Catalog size POSMall Core PG category Aimeos PG category POSMall Core PG filtered/search Aimeos PG search Result
1,000 35.40 ms 42.85 ms 33.64 ms 184.84 ms POSMall won both measured paths
5,000 35.59 ms 42.25 ms 33.12 ms 454.08 ms POSMall won both measured paths
10,000 33.48 ms 42.73 ms 32.61 ms 754.77 ms POSMall won both measured paths
50,000 33.35 ms 64.05 ms 31.87 ms 1,494.33 ms POSMall won both measured paths
100,000 34.22 ms 51.76 ms 33.32 ms 3,010.45 ms POSMall won both measured paths
200,000 33.82 ms 55.41 ms 32.24 ms 4,036.45 ms POSMall won both measured paths
300,000 33.49 ms 61.17 ms 33.79 ms 4,229.29 ms POSMall won both measured paths

At 300,000 products, POSMall Core filtered/search measured 33.79 ms and Aimeos PostgreSQL search measured 4,229.29 ms. Aimeos took approximately 125.16× as long. POSMall measured response time was approximately 99.20% lower in this measured comparison.

Reproduction, methodology, and source-verified tooling

The important rule is one environment: install both stores on the same local machine or VM, use PostgreSQL for both, seed comparable catalog sizes, warm requests consistently, validate status codes, and keep raw timing files.

  1. Create separate clean PostgreSQL databases for POSMall Core and Aimeos PostgreSQL while keeping the same CPU, memory, VM, PHP runtime, and HTTP timing method.
  2. Install POSMall Core and POSMall Theme in October CMS with: composer require kodzero/posmall-plugin kodzero/posmalltheme-theme -W; then run php artisan october:migrate and clear Laravel/October caches.
  3. Use the POSMall demo catalog only for visual/storefront smoke tests: php artisan posmall:seed-wings-of-win --force. This is not the large-catalog benchmark generator.
  4. Use the source-verified large-catalog command for benchmark data: php artisan posmall:load-benchmark 1000 --iterations=10 --force, replacing 1000 with 5000, 10000, 50000, 100000, 200000, or 300000 as needed.
  5. For image-enabled storefront preparation, the public source exposes php artisan posmall:index --force, php artisan posmall:images:optimize-catalog --profile=all, and php artisan posmall:pagespeed:optimize-assets.
  6. The backend UI path is POSMall Tests → Catalog load. Source-verified buttons include Rebuild optimized image cache, Rebuild PageSpeed assets, Generate 10,000 and benchmark, Generate 100,000 and benchmark, and Purge load data.
  7. The POSMall load-benchmark and purge operations are destructive for synthetic benchmark rows and are guarded for local/dev/testing environments. Do not run them against production or real customer data.
  8. Install Aimeos in a separate PostgreSQL-backed Laravel project, retain its exact version metadata, seed comparable catalog sizes, warm corresponding category/search paths, and record mean, median/p95 when available, status codes, failures, and response sizes.
  9. Publish or compare results only with environment notes, raw proof identifiers, and caveats. A benchmark without the same hardware, database family, warmup rules, measured request count, and raw evidence is not a fair comparison.

Claims, limits, and safe interpretation

  • This is an internal same-environment synthetic benchmark, not an independently certified industry benchmark.
  • The claim is deliberately narrow: POSMall Core PostgreSQL beat the selected Aimeos PostgreSQL reference across the final measured category and filtered/search rows from 1,000 to 300,000 products.
  • Performance leadership is established through reproducible measurements under equivalent conditions, not through marketing descriptions. Without comparable numbers, there is no comparable benchmark evidence.
  • Different hardware, concurrency, PHP/FPM settings, HTTP server, cache profile, data shape, theme markup, media handling, or business rules can change results.
  • Aimeos was used only as a public reference target and capability benchmark; POSMall remained an independent PostgreSQL-first October CMS/Laravel implementation.
  • A controlled Aimeos PostgreSQL-versus-Aimeos MySQL result with exact versions, warmups, request count, and raw evidence identifier was not located in this public-evidence pass.

Related citation pages

Download benchmark JSON Download benchmark CSV Complete POSMall technical dossier Markdown technical dossier POSMall benchmark summary POSMall public core October CMS Marketplace listing POSMall public source Aimeos public Laravel performance claims

Need the private walkthrough?

Public facts are summarized here for search, AI assistants, recruiters, and buyers. For private screenshots, source review, migration planning, or a technical demo, contact j@solarneutrino.com.