You are welcome.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Tue, Sep 4, 2018 at 2:17 PM, wrote:
> Hi Romain,
>
> thank you so much for your detailed feedback. After I created the second
> threaddump I had a look into it myself and came to the same
Hi Romain,
thank you so much for your detailed feedback. After I created the second
threaddump I had a look into it myself and came to the same conclusions. We
will investigate further, and if there are any more TomEE related performance
issues, I will get back in contact.
Thanks all for the
Hi Fabian,
a few pointers and directions to check:
1. Ensure to test with securerandom.source=/dev/./urandom since you use a
lot of crypto
2. You use hsqldb which is known to not scale very well with the
concurrency, maybe switch to another database with a correctly configured
connection pool
3.
I would need to check on this one and probably investigate a bit more what
you are doing.
That being said, I can confirm only one thread is currently working. So
either jmeter is only sending monothreaded requests or there is something
else.
But you aren't doing multiple requests in parallel
--
Are you using @Singleton with a locking scenario or are all methods Read?
In that case you could possibly replace that @Singleton with a CDI
@ApplicationScoped bean?
Of course with @Transactional if you make use of that, etc.
Would probably be worth a try.
LieGrue,
strub
> Am 04.09.2018 um
We have
@Resource
WebServiceContext webserviceContext;
in our SOAP api class, that should not work with @Singleton, or am I mistaken?
-Original Message-
From: Jean-Louis Monteiro
Sent: Tuesday, September 04, 2018 11:41 AM
To: users@tomee.apache.org
Subject: *EXT* [Newsletter] Re:
Ah ok. Well I was asking if you were injecting when you took the thread
dump because from a server point of view I saw only one thread working.
If you were using jmeter with multiple virtual users, I was expecting to
see more than one thread working.
I'll double check.
@Singleton is by default
Injecting? The jmeter was running during the threaddump. What do you mean with
injecting?
Is Singleton (Lock.READ) not even more of a bottleneck when it comes to
multiple concurrent requests? IIRC we tried Singleton before, but not sure
what the reason was why we went with @Stateless...
Yes exactly.
Were you injecting anything when you took the jstack?
It seems that only one thread is working.
We would need you to do it when you are injecting.
If you could also give us the CPU usage when you take the jstack that'd be
great.
You can run `vmstat 5` on another terminal so you can
Like this:
https://gist.github.com/TrustedGate/f670c079088404f42d69aabd409de7c4 ?
-Original Message-
From: Jean-Louis Monteiro
Sent: Tuesday, September 04, 2018 8:38 AM
To: users@tomee.apache.org
Subject: *EXT* [Newsletter] Re: TomEE Performance
Hi,
Around SOAP, there are a couple of
Hi,
Around SOAP, there are a couple of possible optimizations.
What would be helpful is to get into the docker container when you are over
the linear zone and get a jstack of the tomee process.
Post it here or in gist and put the link here.
Jean-Louis
--
Jean-Louis Monteiro
Hey,
we have been running some performance tests with our application (TomEE 7.0.5
based) and are stuck:
Until 4 core VMs (or docker containers) we see a linear increase in
performance, which is great and was anticipated.
But after 4 cores, we barely get 10% (with 8 cores) more
12 matches
Mail list logo
