About slow

71-80 of 81Refresh
Forum
1

Suspected memleak caused by bad state of EntityManager

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
Issue
1

Threaded Test - Failed to commit transaction: Unexpected internal exception

 - temporary files are used, which is very slow. I found out that using the following hint helps
Forum
1

To open source, or not to open source

Hi, We are currently using db4o with a commercial licence, but finds it very frustrating after they have been taken over by Versant. The development of db4o is going very slow and major bugfixes are not been backported to stable releases, but only put into bleeding edge branches
Forum
1

Update Entity references if we change the type of an entity

well as its subclasses and your sample test passes. However, please note that: It may slow
Issue
1

Use temporary files to enable very large transactions

only if there are no other options. It is also slow. A much better solution (faster and with unlimited
Forum
1

Future JDO versions?

is slow, and there are only a few JDO features that are currently not supported by ObjectDB. The main
Forum
1

Failover from Master to Slave

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

again merger missing logs + objectdb exception

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

Java 9 support

server provided by Amazon Web Services (a "t2.nano", which has only a single slow CPU and only 0.5 GiB
Forum
1

Objectdb EntityManagerFactory problem

an EntityManagerFactory is relatively slow. It is usually better to use one EntityManagerFactory