Hammoud,
as soon as LAN comes into play (which is typical in enterprise computing) the performance difference inside of Java VM is by far not your biggiest problem, since LAN is many times slower than you CPU and RAM. That's why I said, architecture and design are the major performance influences, while the actual O/R technology is not. So the actual performance benefit in a real world scenario doesn't come from intrinsic JPA or JDBC benefits, but from the implied architectural or design targets (JPA: client cache, JDBC: server cache). You can find an architecture or scenario that fits pretty well on each of these technologies to proof that it is of higher performance than the other one. So none of these technologies is superior to the other. It solely depends on the use case. That's why I said in the beginning, it is comparin apples and bananas. ;-)
Have Fun
Markus
-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: Donnerstag, 10. Juli 2008 18:29
To: users_at_glassfish.dev.java.net
Subject: Re: RE: Re: RE: Re: Re: JPA: speed vs JDBC
Hi Markus,
> Client-/Server computing
Have to consider about extending my single server to typical client/server sooner or later:)
> In sum, you have far more LAN transport with JDBC than with JPA
That makes really sense.
Did not include LAN traffic in my consideration.
thanx for clearing my issues,
Hammoud
[Message sent by forum member 'hammoud' (hammoud)]
http://forums.java.net/jive/thread.jspa?messageID=285715
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net