ObjectDB Database Search

(and enhancement) it persists 340,000 objects per second ". Insertion Speed Rate and Batch Load Now, ten years later, I run it on Intel Core i5-5300U (2.3Ghz) with 8GB memory, output is 45000 per second ... ? After the augment of em.clear(), output changes to 301000 per second . It still below your original InsertTest

, because sometimes it doesn't work, but you don't know. It's the second time when I encounter this bug in 2 ... can be found, so I don't have to modify this second project, because this is much larger ... , without needing to redeploy/run the app the second time (after the wrong numbers are printed

the second junit test, you will see heaps of calls like: AttributeName EQUALS method called ... only at the database id.   Second issue. The docs at: http://www.objectdb.com/api/java/jpa/OneToMany state ... if you describe your expectations more clearly. In the second problem - do you expect disabling cascading through keys

is enabled. support Support L2 cache? I'm not sure. But why the second find() will output? By the way, a query "select e from nodes e" will be ok regardless of the first time or the second time ... I'm doubting the example in jpab.jar runs twice in each test and choose only the second result, maybe

a parameter argument for the second outer query. support Support You may try splitting the query ... argument for the second outer query. Your suggestion is not feasible. I want to get a list of extinct ... the result collection as a parameter argument for the second outer query. gzdillon Lai Yang The inner query

.objectdb.Doctor.main(Doctor.java:22) [ObjectDB 2.1.1_04] Java heap space and second try: odb@devodb ... well with the default configuration - it took ~10 seconds to check the database and additional 20 seconds to rebuild a new database. With 256MB max heap size I got the same  OutOfMemoryError

everything is ok. Afterwards i added the replication tag to the configuration of the second server and started it. The second server starts complaining instantly with the following Exception: com.objectdb ... .Thread.run(Thread.java:722) This message is repeated every few seconds . I already tried to fix

, ObjectDB should automatically switch to the second URL and promote it as master, and DB ... may have to be delayed a few seconds to let all live applications see the change, but a delay of a few seconds should be acceptable in most applications. support Support Hello, ragarding switching from

of them has a parent and some childs) it takes about 70 seconds . Doing the same iteration with items that are not ... about 37 seconds and "objectdb.java.util.ArrayList.iterator" takes about 33 seconds doing

at the output from the second junit test, you will see heaps of calls like: AttributeName EQUALS method ... to look only at the database id. Second issue. The docs at: http://www.objectdb.com/api/java/jpa ... described as issue #618 . A fix will not be available immediately. It is unclear if the second

it at '0' all the way to '10000' (10 seconds ) I can't accomplish this. The ideal case ... ; I used  5 seconds (5000 milliseconds) and I never saw the issue again. I assume you are using

Hi, I make a full binary tree of 4095 node, I check the first 9 node, but the root cost 24 seconds , why? Result: =========== find time @ 24.125000 getSons time @ 0.000000 1 : type:Nodes, sons:2 ... = (System.currentTimeMillis()-start)/1000f;   System.out.printf("Insert: %f objects per second %n", iNum

; Everything works fine when running with one thread, however, when adding a second thread some ... objects and then the second query for the organisations returns 800 objects as expected.   eitane

/ setters ... } when I query by the "state" field in TestEntity it tooks several seconds to retrieve ... the second entity completely and integrate its 3 variables directly in the TestEntity... but it makes

(); c1.increase(); // Second user retrieves and updates the Counter:   PersistenceManager pm2 ... ().commit(); pm1.close(); // Second user commits - fails with JDOOptimisticVerificationException

.MINUTE, 0);         cal.set(Calendar. SECOND , 0);    ... ;       cal.set(Calendar. SECOND , 0);       

a few seconds after it becomes accessible again. Inactivity Timeout You can set the inactivity timeout  in seconds and it affects both the client and the server side:       

I have a call to getObjectsById(Collection,boolean) that is throwing a JDOException the first time I'm attempting to retrieve an object. If I try again, then the second request succeeds. Any idea ... getting. Your advice to ignore them explains why it would work the second time around.  I believe

In our production environment, entity manager creation, the line below, sometimes take upto few ten's of seconds to create. Is there any reason that is known which may be causing this ? Any ... seconds to return. CAPdev CAP Dev Is it client-server mode or embedded mode? If client-server mode

Hello, I have a problem with the following situation. I insert persons with addresses. In the first run, they are all new with a new address. It runs fast. In the second run, the persons are all loaded and got a second address. This seams to be much slower. The Entities are all enhanced by

, DAY , HOUR , MINUTE , SECOND ) was just added to ObjectDB in build 2.2.8_02. For example ... ;     "HOUR(e.t), MINUTE(e.t), SECOND (e.t) FROM MyEntity e",    

collections in the first pack of queries and non-zero size results in the second pack ? I ... , minutes, seconds , and milliseconds are 0, but relative to UTC. Therefore, the parameter to the query

({t '23:59:00'}) is evaluated to 59. SECOND ({t '23:59:00'}) is evaluated to 0. Quite often I ... ) - Extracts the time part (hour, minute, second , millisecond) as a Date instance. Please try

queries increased with this database size to an unacceptable rate (several seconds compared ... for query like this (400000 ObjectNode instances, database size around 1.5 GByte): around 1.5 seconds

Second persist of FirstEntity Transaction: 1 Persist: 0 First persist of SecondEntity Transaction: 117 Persist: 103 Second persist of SecondEntity Transaction: 2 Persist: 0

run in parallel. The first transaction is closed before the second transaction will be opened ... again, or we wait a certain time (maybe 10-20 seconds ) after opening the database before we execute

.EAGER) . It is little bit faster as before. But also this configuration needs 80 seconds in comparing to @Basic (60 seconds ). btc_es BTC EmbeddedSystems Another possible difference

.objectdb.test2' This second app makes some queries and should not change the content of the db ... of entries is zero. - running the app a second time, the count is zero and the average is null

but the am not able get second one ( System.setProperty("objectdb.temp.no-schema-downgrade", "true ... The second setting is expected to stop ObjectDB from returning to a list of fields that was used in

.BB ( second position before the change) now are set to ENUM.CC ( second position after the change

to set the lock, too. On exception we wait and retry - the first thread commits but the second ... .awaitTermination(5, TimeUnit. SECONDS ); emf.close(); } private static void initDB() { EntityManager em = emf

- what happen to the second process which was waiting for the lock? does the second process continue and try

Opening an EntityManagerFactory and an EntityManager should never take 30 seconds . Most ObjectDB ... there is roughly a 30 second delay each time I open the jar/switch connections while running with java

I just uploaded two more heap dumps: one with only live objects, second one with all objects right ... that should take about 2-3 seconds on cold database now finish in 300ms: 2012-09-20 11:15:19.139 [http-bio-8080

about 9-11 seconds to render webpage: 2011-03-11 13:08:05.552 [http-18080-exec-3] INFO  Click ... less in middle at about 5-6 seconds . There is about 14k objects of this type in this database. ODB

is also closed. Currently ObjectDB waits up to 2 seconds for that thread on close. If your close ... ;Is the timeout for closing purger threads configurable, so I could try raising it? No, but the 2- seconds

-keep-alive- seconds 60 thread-queue-capacity 2147483647 allow-core-thread-timeout false INFO: SEC1002 ... EjbThreadPoolExecutor with thread-core-pool-size 16 thread-max-pool-size 32 thread-keep-alive- seconds 60

Transaction per second limit and making sure if ObjectDB can help us here. Additionally the only cache I ... if that is possible -- but want to know what is the Transaction per second that ObjectDB can shoot

" is missing at the end of the query. Please check the query. Second , if there is an internal ... and you will see no problems with this query Second , I have attached a) Screenshot for used ObjectDb version b) Original

seconds . Could you please check running that query in the Explorer? support Support Execution time ... -var-order=p1]] execution time around 60 seconds Query plan 1/16 description

which is correct, the second query also returns 1 result but 0 tags which is obviously wrong ... , for the second query 1 year in the past. Otherwise there would be no bug. My provided test case

the second query. Do I need to call refresh() on the object, query, or EntityManager? ps: setting ... at all, I was expecting that the object would be returned in the second query. That doesn't happen

use a second database. Within the real transaction we work with a copy of this database. This enables us to repeatedly commit on the second database and in case of a fault we can still recover

) or (p1.name = "startableState" and p1.doubleValue = 0)) 2.7.6 takes around 4 seconds 2.7.6_04 takes 200 seconds and reports in query plan:   Query plan 1/2 description

and have activated the license.  My application is persisting about 1000 of these each second from among 500 active threads.  Between each persist, the thread sleeps for half a second . 

and prepare final results. Second query (which fails): Query Plan Description ... results. quasado Alexander Adam By the way, the second query also has way too many executions in

Hi! We have an two entities, the first one is something like: @Embeddable class TestEmbed {...} and the second one: @Entity class TestEntity { private TestEmbed myEmbed = null; public TestEmbed ... for which I use and store a string now. but it seems the second issue is really having an embeddable

, it was created when a query that normally takes around 5 seconds was terminated by the timeout that we have set (200 seconds ) ad 2: unfortunately we cannot step back and we are not able to step

the buildProject(String name) method a second time in a row (in recent versions of ObjectDB only): Info ... -OK-when-force-commit.png   But then, when the commit() is executed on the second build pass, I

; If we try to ecexute a Query (in the second main method): TypedQuery q = em.createQuery("SELECT c ... . If these changes are done separately, i.e. the database is opened between the first and the second