You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Martijn Dashorst <ma...@gmail.com> on 2018/11/22 14:23:01 UTC
Jetty & ab issue in quick start?
When I try to run a somewhat longer benchmark with our Quick Start
application, I get strange timeouts while running ab (or siege)
ab -n 100000 -c 4 http://localhost:8080/
This is ApacheBench, Version 2.3 <$Revision: 1826891 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd
Licensed to The Apache Software Foundation
Benchmarking localhost (be patient)
Completed 10000 requests
apr_socket_recv: Operation timed out (60)
Total of 16347 requests completed
The ab runs always fail at the 16348th request (when you use
concurrency > 1 it will vary around 16348)
I've upgraded/downgraded Wicket (this is still the case with 7.0,
7.10, 8.0, 8.1 and 8.2).
I've upgraded jetty to the latest 9.4 version (9.4.14.v20181114) to no avail.
Running ab on a remote Tomcat server does end normally, so it doesn't
appear to be ab related (also siege exhibits the same behavior on the
local Jetty server).
Can anyone confirm this odd behavior?
Martijn
Re: Jetty & ab issue in quick start?
Posted by Maxim Solodovnik <so...@gmail.com>.
Have tested with 8.2.0 quickstart:
Percentage of the requests served within a certain time (ms)
50% 0
66% 0
75% 0
80% 0
90% 1
95% 1
98% 1
99% 2
100% 231 (longest request)
Ubuntu 16.04, no errors
On Fri, 23 Nov 2018 at 01:43, Sven Meier <sv...@meiers.net> wrote:
> Hi Martijn,
>
> works fine here.
>
> Sven
>
>
> ab -n 100000 -c 4 http://localhost:8080/
> This is ApacheBench, Version 2.3 <$Revision: 1807734 $>
> Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
> Licensed to The Apache Software Foundation, http://www.apache.org/
>
> Benchmarking localhost (be patient)
> Completed 10000 requests
> Completed 20000 requests
> Completed 30000 requests
> Completed 40000 requests
> Completed 50000 requests
> Completed 60000 requests
> Completed 70000 requests
> Completed 80000 requests
> Completed 90000 requests
> Completed 100000 requests
> Finished 100000 requests
>
>
> Server Software: Jetty(9.4.12.v20180830)
> Server Hostname: localhost
> Server Port: 8080
>
> Document Path: /
> Document Length: 2317 bytes
>
> Concurrency Level: 4
> Time taken for tests: 26.669 seconds
> Complete requests: 100000
> Failed requests: 0
> Total transferred: 253800000 bytes
> HTML transferred: 231700000 bytes
> Requests per second: 3749.71 [#/sec] (mean)
> Time per request: 1.067 [ms] (mean)
> Time per request: 0.267 [ms] (mean, across all concurrent requests)
> Transfer rate: 9293.70 [Kbytes/sec] received
>
> Connection Times (ms)
> min mean[+/-sd] median max
> Connect: 0 0 0.2 0 6
> Processing: 0 1 1.1 1 33
> Waiting: 0 1 1.0 0 33
> Total: 0 1 1.1 1 33
>
> Percentage of the requests served within a certain time (ms)
> 50% 1
> 66% 1
> 75% 1
> 80% 1
> 90% 2
> 95% 3
> 98% 4
> 99% 5
> 100% 33 (longest request)
>
>
>
>
> Am 22.11.18 um 15:23 schrieb Martijn Dashorst:
> > When I try to run a somewhat longer benchmark with our Quick Start
> > application, I get strange timeouts while running ab (or siege)
> >
> > ab -n 100000 -c 4 http://localhost:8080/
> > This is ApacheBench, Version 2.3 <$Revision: 1826891 $>
> > Copyright 1996 Adam Twiss, Zeus Technology Ltd
> > Licensed to The Apache Software Foundation
> >
> > Benchmarking localhost (be patient)
> > Completed 10000 requests
> > apr_socket_recv: Operation timed out (60)
> > Total of 16347 requests completed
> >
> > The ab runs always fail at the 16348th request (when you use
> > concurrency > 1 it will vary around 16348)
> >
> > I've upgraded/downgraded Wicket (this is still the case with 7.0,
> > 7.10, 8.0, 8.1 and 8.2).
> >
> > I've upgraded jetty to the latest 9.4 version (9.4.14.v20181114) to no
> avail.
> >
> > Running ab on a remote Tomcat server does end normally, so it doesn't
> > appear to be ab related (also siege exhibits the same behavior on the
> > local Jetty server).
> >
> > Can anyone confirm this odd behavior?
> >
> > Martijn
>
--
WBR
Maxim aka solomax
Re: Jetty & ab issue in quick start?
Posted by Sven Meier <sv...@meiers.net>.
Hi Martijn,
works fine here.
Sven
ab -n 100000 -c 4 http://localhost:8080/
This is ApacheBench, Version 2.3 <$Revision: 1807734 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/
Benchmarking localhost (be patient)
Completed 10000 requests
Completed 20000 requests
Completed 30000 requests
Completed 40000 requests
Completed 50000 requests
Completed 60000 requests
Completed 70000 requests
Completed 80000 requests
Completed 90000 requests
Completed 100000 requests
Finished 100000 requests
Server Software: Jetty(9.4.12.v20180830)
Server Hostname: localhost
Server Port: 8080
Document Path: /
Document Length: 2317 bytes
Concurrency Level: 4
Time taken for tests: 26.669 seconds
Complete requests: 100000
Failed requests: 0
Total transferred: 253800000 bytes
HTML transferred: 231700000 bytes
Requests per second: 3749.71 [#/sec] (mean)
Time per request: 1.067 [ms] (mean)
Time per request: 0.267 [ms] (mean, across all concurrent requests)
Transfer rate: 9293.70 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.2 0 6
Processing: 0 1 1.1 1 33
Waiting: 0 1 1.0 0 33
Total: 0 1 1.1 1 33
Percentage of the requests served within a certain time (ms)
50% 1
66% 1
75% 1
80% 1
90% 2
95% 3
98% 4
99% 5
100% 33 (longest request)
Am 22.11.18 um 15:23 schrieb Martijn Dashorst:
> When I try to run a somewhat longer benchmark with our Quick Start
> application, I get strange timeouts while running ab (or siege)
>
> ab -n 100000 -c 4 http://localhost:8080/
> This is ApacheBench, Version 2.3 <$Revision: 1826891 $>
> Copyright 1996 Adam Twiss, Zeus Technology Ltd
> Licensed to The Apache Software Foundation
>
> Benchmarking localhost (be patient)
> Completed 10000 requests
> apr_socket_recv: Operation timed out (60)
> Total of 16347 requests completed
>
> The ab runs always fail at the 16348th request (when you use
> concurrency > 1 it will vary around 16348)
>
> I've upgraded/downgraded Wicket (this is still the case with 7.0,
> 7.10, 8.0, 8.1 and 8.2).
>
> I've upgraded jetty to the latest 9.4 version (9.4.14.v20181114) to no avail.
>
> Running ab on a remote Tomcat server does end normally, so it doesn't
> appear to be ab related (also siege exhibits the same behavior on the
> local Jetty server).
>
> Can anyone confirm this odd behavior?
>
> Martijn