-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
 Post subject: Query performance before flush
PostPosted: Mon Sep 19, 2011 10:29 am 
Newbie

Joined: Mon Jun 27, 2011 4:51 am
Posts: 1
When large amount of records is instantiated (like 100000)
Looking for a record by ID (32 bytes of UUID) is much much slower before flushing to the database.
Seems that before flushing the search is simply looking for the matching record without using any indexing.
When accessing the database, it takes few milliseconds.


Top
 Profile  
 
 Post subject: Re: Query performance before flush
PostPosted: Tue Sep 20, 2011 4:59 am 
Hibernate Team
Hibernate Team

Joined: Thu Apr 05, 2007 5:52 am
Posts: 1689
Location: Sweden
Hi,

I don't understand what you are saying/asking. When you are saying "looking for a record by id", do you mean doing a fulltext search for the record? Or what do you do? Regarding fulltext search, if your objects are newly created and you are relying on automatic indexing you will have to commit your transaction before you can even search, because per default the indexing will occur at commit time.

Maybe you can clarify what your question is?

--Hardy


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.