On Thu, Mar 14, 2019 at 2:58 PM Santhosh Kumar
wrote:
> I have tried the same set of testcases using h2load with tomcat 9.0.17
> from github releases
> (https://github.com/apache/tomcat/releases/tag/9.0.17) .
>
> h2load -n 100 -d /tmp/1k https://localhost:8443/
> requests: 100 total, 64 started,
I have tried the same set of testcases using h2load with tomcat 9.0.17
from github releases
(https://github.com/apache/tomcat/releases/tag/9.0.17) .
h2load -n 100 -d /tmp/1k https://localhost:8443/
requests: 100 total, 64 started, 63 done, 63 succeeded, 37 failed, 37
errored, 0 timeout
h2load -n
On Thu, Mar 7, 2019 at 5:22 PM Rémy Maucherat wrote:
> On Thu, Mar 7, 2019 at 2:54 PM Rémy Maucherat wrote:
>
>> On Thu, Mar 7, 2019 at 1:47 PM Mark Thomas wrote:
>>
>>> On 07/03/2019 07:40, Santhosh Kumar wrote:
>>> > From some of the test cases I can safely say that tomcat is hitting
>>>
On Thu, Mar 7, 2019 at 2:54 PM Rémy Maucherat wrote:
> On Thu, Mar 7, 2019 at 1:47 PM Mark Thomas wrote:
>
>> On 07/03/2019 07:40, Santhosh Kumar wrote:
>> > From some of the test cases I can safely say that tomcat is hitting some
>> > limits, I have two test cases ran with two diff size of
I have executed few test cases in both NIO and NIO2 as Mark has requested
for testing NIO connector.
--Below is
NIO
h2load -n50 -c1 -m1 --header="Content-Type:application/json" -d
On Thu, Mar 7, 2019 at 1:47 PM Mark Thomas wrote:
> On 07/03/2019 07:40, Santhosh Kumar wrote:
> > From some of the test cases I can safely say that tomcat is hitting some
> > limits, I have two test cases ran with two diff size of payload and
> without
> > any queryParams. The servlet is a
On 07/03/2019 07:40, Santhosh Kumar wrote:
> From some of the test cases I can safely say that tomcat is hitting some
> limits, I have two test cases ran with two diff size of payload and without
> any queryParams. The servlet is a empty servlet just returns after
> receiving without doing any
>From some of the test cases I can safely say that tomcat is hitting some
limits, I have two test cases ran with two diff size of payload and without
any queryParams. The servlet is a empty servlet just returns after
receiving without doing any business side logic
h2load -n100 -c1 -m1
When you run your test(s), does it fail after a certain period of
time, or just keep on going under a certain number of requests?
Also, to confirm: you're sending 1000 Byte + query strings?
Are you doing anything in the server side component to verify that
your parameters have been received
I hope so, I used updated packages/components at the time of development.
few may be outdated like tomcat native as I was using 1.2.18 while
developing but 1.2.21 got released recently.
On Wed, Mar 6, 2019 at 6:18 PM John Dale wrote:
> Have you upgraded to the most recent release of your major
Have you upgraded to the most recent release of your major version?
If so, and if this issue still persists, it is something that the core
development team might want to look at assuming they can replicate the
issue.
On 3/5/19, Santhosh Kumar wrote:
> Sometimes more than 10x
>
> On Tue, Mar 5,
Sometimes more than 10x
On Tue, Mar 5, 2019 at 10:00 PM John Dale wrote:
> How many orders of magnitude slower are the post requests?
>
> On 3/5/19, Santhosh Kumar wrote:
> > I was testing in the localhost
> >
> > On Tue, Mar 5, 2019 at 9:32 PM John Dale wrote:
> >
> >> Are you running your
How many orders of magnitude slower are the post requests?
On 3/5/19, Santhosh Kumar wrote:
> I was testing in the localhost
>
> On Tue, Mar 5, 2019 at 9:32 PM John Dale wrote:
>
>> Are you running your test client (h2load) on the same machine, same
>> network, or is it over the net (so, like
I was testing in the localhost
On Tue, Mar 5, 2019 at 9:32 PM John Dale wrote:
> Are you running your test client (h2load) on the same machine, same
> network, or is it over the net (so, like 20ms latency on each
> request)? The reason I ask is that if you are local (especially), it
> may
Are you running your test client (h2load) on the same machine, same
network, or is it over the net (so, like 20ms latency on each
request)? The reason I ask is that if you are local (especially), it
may queue up too many requests for tomcat to handle in the testing
period with its thread pool.
Bytes
On Tue, Mar 5, 2019 at 9:28 PM John Dale wrote:
> 1000-1500 MB or KB?
>
> On 3/4/19, Santhosh Kumar wrote:
> > As per the documentation,
> >
> https://tomcat.apache.org/tomcat-9.0-doc/config/http.html#SSL_Support_-_SSLHostConfig
> >
> > this connector supports maxPostSize, by default the
1000-1500 MB or KB?
On 3/4/19, Santhosh Kumar wrote:
> As per the documentation,
> https://tomcat.apache.org/tomcat-9.0-doc/config/http.html#SSL_Support_-_SSLHostConfig
>
> this connector supports maxPostSize, by default the limit is set to 2MB
>
> On Tue, Mar 5, 2019 at 5:09 AM John Dale
As per the documentation,
https://tomcat.apache.org/tomcat-9.0-doc/config/http.html#SSL_Support_-_SSLHostConfig
this connector supports maxPostSize, by default the limit is set to 2MB
On Tue, Mar 5, 2019 at 5:09 AM John Dale wrote:
> Does anyone know if this connector supports maxPostSize
Does anyone know if this connector supports maxPostSize parameter?
On 3/4/19, Santhosh Kumar wrote:
> Hi,
>
> We have a tomcat instance which is http2 enabled and it needs to serve
> large number of requests using multiplexing, so we have configured our
> instance as follows,
>
>
Nice test case. Is the JVM able to garbage collect fast enough? Are
you releasing the resources properly in your components as early as
possible? Java VM's achieve a steady-state after a certain period of
time, but I've found in some cases garbage collection doesn't keep-up
with my load tests
> Do you actually need all those values and where do they come from in the
first place ? Do you understand what they do ?
I was just experimenting with all available attributes related to socket
and multiplexing. I have followed the documentations,
On Mon, Mar 4, 2019 at 10:40 AM Santhosh Kumar
wrote:
> Hi,
>
> We have a tomcat instance which is http2 enabled and it needs to serve
> large number of requests using multiplexing, so we have configured our
> instance as follows,
>
> sslImplementationName="org.apache.tomcat.util.net
>
22 matches
Mail list logo
