Hi Christophe!
I don´t think MS Access is an issue here.
Usually Access is a lot faster than real Client/Server DB Engines
principally because it has nothing to do with them, it is almost a raw file
on your disk.
What may be an obstacle is the JDBC-ODBC bridge, that is slower than a
native JDBC driver.
As far as I know the real problem must be the Entity Bean pool. If the pool
is not filled up at start time then a "new" must be performed every time you
issue a create() method against the home object. This is true until the
number of instances of the Entity Bean class reaches the maximum pool size.
Question: when you test the server with 10,000 creates() do you request
Entity Beans with the same or different primary keys?
Thanks.
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 15, 2001 2:55 PM
Subject: 3 seconds to create an entity bean
> Hello,
>
> I have do a small performance test and I have this results :
> - The server need 3 seconds to create a simple EntityBean
>
> I use JBoss with 128MB and Windows 2000.
> I also use a MS Access database (.mdb) and a JDBC-ODBC Bridge type 1.
>
> I look at the task manager and I cannot see why I have a problem ?
>
> Can someone help me, where can I find some statistics about server
> performance (Comparaisons)
>
> Thanks a lot for your help
>
> Christophe
>
>
===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
