Feature/benchmark workflow

[fr3on]

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing tests pass locally with my changes (composer test)
• PHPStan reports no errors (composer analyze)

[github-actions]

🚀 Quill Performance Metrics

Environment: Ubuntu · PHP 8.3 · quill-core 0.0.2 · 2 workers Quill Core

Quill Binary Benchmark
  > Server     : Quill Core
  > Tool       : wrk
  > Duration   : 5s
  > Connections: 50
  > Workers    : 2
  > Starting Quill server...
  > Server is ready. Running benchmarks...
    Running 5s test @ http://127.0.0.1:8080/hello
      2 threads and 50 connections
      Thread Stats   Avg      Stdev     Max   +/- Stdev
        Latency     1.03ms    0.88ms   9.67ms   83.25%
        Req/Sec    26.39k     3.06k   36.08k    83.00%
      263186 requests in 5.01s, 40.66MB read
    Requests/sec:  52527.03
    Transfer/sec:      8.12MB

  > Benchmarks completed.