|
Hi all,
I'm Sw. Eng. Marco Pappalardo and I'm
developing for Ergotech System Inc. a sw using JBoss and
InstantDb.
I had some troubles about performances and I want
to talk to you about them in order to ask you to let me know if you have some
suggestion.
I'm using a Celeron 500 processor with 128 Mbyte
RAM.
Performing my tests, I noticed my application is
too slow.
I made some tests in order to understand where I
lose my time, seen that I use both java classes and Stateful Session +
Entity Beans.
I had the impression that Session Beans should
cause my troubles. So I made some test to have an idea about Session Beans
Activation and Loading times. As you can see below, times beetween activation
and loading are different but about all are 30 or 40 msecs. Do you think it
is a right time for JBoss to access my Database?
And what time about creation? What can I do to
decrease these times? Do you think I will increase sw performances changing my
database?
Activate: 971289019698
Load: 971289019728
...
Activate: 971289020269
Load: 971289020309
....
Activate: 971289036782
Load: 971289036862
Have you any estimate concernig time spent by the
container asking for data on database? And beetween Session Beans? And beetween
a Session and an Entity Bean?
Do you think Should I have a considerable
increasing if I put my business Logic directly on Entity Beans and avoiding use
of Session Beans?
Is there a way to find out spent time executing my
code and one spent by the container?
I also tried to disable console logging in JBoss
configuration but performances increased too few to be considered!!
I thank you in advance for what you'll do to help me.
Kings Regards,
Marco Pappalardo |
- Re: [jBoss-Dev] Fw: Set Beans Passivation Marco Pappalardo
- Re: [jBoss-Dev] Fw: Set Beans Passivation Sebastien Alborini
