Hi Andrej,
Thanks a lot for taking a loot at the tcpdump data.
> I just had a brief glance over your tcpdump data ... are you sure
> hibernate isn't using a cursor to fetch each row individually?
Pretty sure, yes. I get the same performance when executing the
hibernate-generated query using JDBC
On 20 February 2011 02:05, Clemens Eisserer wrote:
> I use well tuned hibernate fetch profiles to ensure fewest possible
> roundtrips,
> however I am not getting paid well enough to create an appserver tier ;)
I just had a brief glance over your tcpdump data ... are you sure
hibernate isn't usin
Hi Pierre,
Thanks a lot for your reply.
> Your attached file didn't come through.
Hmm, ok.
I uploaded the wireshark-log to: http://93.190.88.182/psql_large_query.bin
> - different execution plan between your app and ssh+psql, which can happen
> if the planning uses/doesn't use your specific para
When executing huge (10kb), hibernate-generated queries I noticed that
when executed remotly over high-latency network (ping to server
200-400ms), the query takes a lot longer to complete.
When the query is executed remotly (psql or jdbc) it takes 1800ms to
execute, when I issue the query in an
Hello,
When executing huge (10kb), hibernate-generated queries I noticed that
when executed remotly over high-latency network (ping to server
200-400ms), the query takes a lot longer to complete.
When the query is executed remotly (psql or jdbc) it takes 1800ms to
execute, when I issue the query
