Hi Howard,
Your discussions are very interesting - I haven't unsubscribed from the
TomEE list yet even though there is such high volume. Lately I
actually
quite enjoy following your progress. There are a lot of emails - but
just
don't get too off-topic ;-) Try a few things on your own, then bring
your
findings to the list. Some questions are a bit off-topic so they're
better
being discussed on other lists.
It's really exciting seeing you using TomEE for the first time and
running
into the initial problems. Those problems are very interesting. When
we
get to discussing Derby vs Hyper vs MySQL however, it's better to do
some
independant research and come back to the list afterwards. (IMHO)
Anyway - I'd love to hear more about how your project turns out, and if
you want some free hosting on our new TomEE cluster, drop me a private
email and I'd be happy to give you some free space. Any experience we
have
with commerical TomEE customers is a great experience for us that we
can
blog about or share with the TomEE devs.
Best Regards,
Neale
----- Original Message ----- From: "Howard W. Smith, Jr." <
smithh032...@gmail.com>
To: <us...@openejb.apache.org>
Sent: Friday, December 14, 2012 5:50 AM
Subject: Re: DB access is very slow
Agreed about Romain, he is very amazing. Noted about HyperSQL, will
avoid
that, and understood about 17mb = "playing". This is a new app that
I've
developed and it's being used every day for 'business', so definitely
not
playing, but I do want to move to prime-time and a faster database, so
I
will do that, ASAP. Thanks Neale.
TomEE committers already admit that TomEE is not 'perfect'...yet, so I
would assume these discussions are welcome. Honestly, I do my best to
make
sure I am on topic. I'm sure TomEE and OpenEJB is responsible for the
@Stateless EJB transaction, triggered by @Schedule, and why is TomEE
performing well with Derby when user click button, and managed beans
call
@Stateless EJB (DAO) to perform database operations... but why is
TomEE
not
allowing my @Stateless EJB with @Schedule method() to perform
well...with
a
large transaction.
I have heard that geronimo has many many issues and does not have a
good
name/reputation, but regardless of the negative chatter I've seen on
stackoverflow about geronimo, I still continue to use TomEE and I
communicate my issues here on the list.
On Thu, Dec 13, 2012 at 1:39 PM, Neale <ne...@metawerx.net> wrote:
HyperSQL is another toy.
The specs below are great, Derby looks good in some cases, bad in
others.
But once again this is a very small test database.
You might get 10% performance increase moving your database from
derby
to
mysql, or you might get a 10% performance loss. If you plan to use
it
commercially, use a real database because you will avoid all the
issues
when the database grows. All our (non-student) databases here are
300mb-12gb. That is a very big difference to 17mb, but it depends on
what
data they store and how long they keep it. 17mb is just "playing".
So
10%
performance difference up or down is not much fun to look at.
Anyway - I don't think this is relevant to the TomEE list, and all
the
users/developers receiving these emails 10-20 times per day are
probably
not interested at all. It's very important to keep the discussion
relevant
so that people don't leave the TomEE list. The list gains more
members
from people seeing relevant information and staying subscribed, so we
shouldn't really discuss this here as it's off-topic.
You are saying your real problem is JPA, so please try on another
database, and cut the problem into smaller pieces. Then you will
quickly
find out if it's a Derby issue, a JPA issue, or a TomEE issue.
If TomEE is performing badly compared to Tomcat or JPA on a
command-line
JVM, then I'm sure the TomEE devs will jump on the issue and fix it
as
soon
as possible. Romain is quite amazing, if he sees a problem with
TomEE,
he
leaps on it! So let's try to limit the number of emails to be real
TomEE
issues so we don't waste his time ;-)
Best Regards,
Neale
