Skip to content

Use another method of communicating the results than trying to echo them #38

Open
@motin

Description

@motin

Many frameworks sets the Content-Length header based on what is actually returned in the actual controller method. When curl requests the resource, it will only save output the length of Content-Length. Any remaining output, such as statements printed/echoed after the framework has run it's course will be omitted with curl in verbose mode warning: Excess found in a non pipelined read.

This means in practice that the "outdata" results are not included in the benchmarking results for these frameworks,:

|framework          |requests per second|relative|peak memory|relative|
|-------------------|------------------:|-------:|----------:|-------:|
|slim-3.0           |             608.14|     0.0|       0.00|     0.0|
|lumen-5.1          |             616.32|     0.0|       0.00|     0.0|
|ze-1.0             |             301.87|     0.0|       0.00|     0.0|
|fuel-2.0-dev       |               0.00|     0.0|       0.00|     0.0|
|bear-0.10          |               0.00|     0.0|       0.00|     0.0|
|laravel-5.1        |               0.00|     0.0|       0.00|     0.0|
|typo3f-3.0         |               0.00|     0.0|       0.00|     0.0|

May I suggest another method of communicating the results than trying to echo them? For instance, they can be written to a file. Also, the memory, time and file results should not be required/communicated when running ab tests.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions