Internal Website Search

Hello, we have a question again regarding query performance. The query: SELECT v FROM Values v WHERE v.step.stepNumber = ? is very slow in comparing to the query: SELECT v FROM Values v WHERE v.stepNumber = ? Can you explain why the first query needs so much time or do you have a hint

all) are affectet which results in a slow but increasing memory consumtion of our server

.)   Pseudocode for the fast and the slow solution FAST: for (i = 0; i

in queries lead to performance penalty, how slow is it and would you recommend something better

We have a big entity object tree in our project. If I use the entityManager.remove(childEntity) method to remove a child entity a entityManager.refresh(parentEntity) is necessary in order to have an updated parent/child object tree in memory. But entityManager.refresh is too slow for our project

Steve Zara Development of JDO in the recent years is slow , and there are only a few JDO features

but might be slow if the database is very large, and may cause issues if there is no sufficient space

) but this is painfully slow when there is a high number of large objects. thumbripper Richard Szurgot Currently

hgzwicker Hans-Georg Zwicker An additional index on  childNodes should help. If it is still slow , try

the temporary file threshold , but that may slow performance. To understand the problem better

all the slaves that they got the update since this could slow transactions. support Support

): public List getExtensionByDate() { em.clear(); // TODO Remove me for production. Testing slow query

Hi,   I've been using Hibernate with JPA, and found it too slow , so am moving my project to use ObjectDB. My Jar is being held inside another application, so I don't want to have to rely on a persistance.xml file being in a particular place. When using Hibernate, I was able

it might be faster than JPA because I am storing objects to avoid apparent relative slowness of 

prolancer Emil Andonov Thanks. Download is very slow and could take many hours

is too slow and inefficient. Thanks. lo Hoel Possibly you may be able to retrieve that information using

We started exploring your question, but the size of the OSGI test case makes progress very slow

that the 1:10 ratio is only for relatively small databases. It is true, however, that it is slow

, if you have a slow query you should provide all the details on that query and its execution

, but still too slow in my opinion. Notice I have a db with at least 1M objects, the only way I want

and it's still not enough. We have 1 ODB Server started without any connections to it, and the sockets are slowing

operation is slow , it may indicate that this timeout may not be sufficient. support Support I am closing

Our application manages the Entities itself, so we close the EntityManager after every creating and using. We find a slow memleak in our application recently, and by trace of Entity construct and finalize, we found the problem is caused by bad state of EntityManager. After first throwing

, and queries on field2 may be slow , since as you wrote an entire database scan is required. Notice

" interfaces like this, so that I am not spending a long time (I'm slow ) programming what I'll

model. It might be a slow query. Maybe indexes on the relevant fields of B could help. support

was concerned that using JDO queries even on the primary key would be slow . The created schema is in fact

Hoel No such known issue. The query looks fine. It could be slow if you have many orders. Indexes

that is either slow to respond or not working properly. That would prevent this scenario. rlgarris Richard

= query.getResultList(); Producing everytime ResultList ( Garbage collection destroy and remake ) slows

.setFirstResult(start).setMaxResults(count).getResultList(); is quite slow . Well, after first request and "warming

this. About the slow lazy loading - a test case that demonstrates it is needed to evaluate this. support Support

priority thread. It also seems that it will be slow as option 2a, as emptying list fields updates

implementations could make the test right but slow . It's would also be really great to put these new

performance from ObjectDB, not exactly sure what the problem is. Try to isolate the slow performance, e.g

.06G v 2.9.0_05 ( slow ) find_1_N_1Y() PT20.812S -1.10G/0.46G find_1_N_1Y() PT26.748S +0.29G/0.86G find_1

may be to enable recording:          This is rarely used, may slow

. With no ability to reproduce the problem (yet) progress is slow , but we are getting closer and hope

property access mode. Fixed a bug in allowing page sizes larger than 64KB (which are not supported by ObjectDB). Fixed an issue of very slow online backup.

because: It is non standard JPA extension. It is inefficient ( slow ). But it should work

; This caused the ID lookups on non-existent entities to be " slow " due to an internal exception (thrown

maybe by users?), which may cause a general slowness . support Support the problem

Fixed a bug in the new option to slow backup in client-server mode (see feature request #2681 ).

Added automatic creation of the log directory if it does not exist. Added support of old Spring Framework versions (with JPA 1.0). Fixed "InternalException: InterruptedException" due to application interrupts in embedded mode. Fixed a class loading conflict with Log4j. Fixed very slow processing

ObjectDB supports encryption of client-server communication over the network using SSL . Encryption of data in database files is less commonly used, since it slows the database. In addition, when necessary, external encryption can be used (e.g. at the operating system level

the exception will help. support Support Sorry for the slow reply, I've been away for a couple of days

queries. Fixed a possibly very slow query execution when using entity parameters. Fixed issues in navigation through detached objects .

Hi, I have observed that 500 Mb objectDb database opening time is very slow (~3 seconds) for following code long time = System.currentTimeMillis(); m_EntityMgrFactory = Persistence.createEntityManagerFactory( "objectdb:" + aFilename ); m_EntityManager = m_EntityMgrFactory.createEntityManager

the query more complex and slow unnecessarily (e.g. for the OR query in your post), so any

Added an option to slow backup (see feature request #268 1).