qthttpserver

Commit Graph

Author	SHA1	Message	Date
Matthias Rauter	7b1ada7472	Remove unused variable in benchmark Pick-to: 6.9 6.8 Change-Id: I7908dc0e61080d7524ad9a929f38ee708890fb70 Reviewed-by: Øystein Heskestad <oystein.heskestad@qt.io> Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>	2025-03-28 07:22:58 +01:00
Mårten Nordheim	2c2dc9e15c	Add a benchmark for QHttpServer It's quite simple, we just download a 100MB payload from ourselves and discard all the bytes. The default qbytearray non-TLS case takes around 250ms to complete on my machine, while the TLS case clocks in at around 800ms. Some of this benchmark will measure the time it takes to read as well, but even using an external process to perform the download we would still have to wait for it to receive all the data. Pick-to: 6.8 Change-Id: I0fb700b2f3ab5d73a81f673688ec9404a6749daa Reviewed-by: Mate Barany <mate.barany@qt.io>	2024-09-12 21:22:02 +02:00

Author

SHA1

Message

Date

Matthias Rauter

7b1ada7472

Remove unused variable in benchmark

Pick-to: 6.9 6.8
Change-Id: I7908dc0e61080d7524ad9a929f38ee708890fb70
Reviewed-by: Øystein Heskestad <oystein.heskestad@qt.io>
Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>

2025-03-28 07:22:58 +01:00

Mårten Nordheim

2c2dc9e15c

Add a benchmark for QHttpServer

It's quite simple, we just download a 100MB payload from ourselves and
discard all the bytes.

The default qbytearray non-TLS case takes around 250ms to complete on my
machine, while the TLS case clocks in at around 800ms.

Some of this benchmark will measure the time it takes to read as well,
but even using an external process to perform the download we would
still have to wait for it to receive all the data.

Pick-to: 6.8
Change-Id: I0fb700b2f3ab5d73a81f673688ec9404a6749daa
Reviewed-by: Mate Barany <mate.barany@qt.io>

2024-09-12 21:22:02 +02:00

2 Commits