 1 | is at maximum 30% of activity under heavy load but database queries are let's say not at the speed |
1 | should these be about the same speed? Retrieval by ID is expected to be faster, because it enables direct |
1 | this issue. Fix works perfectly well. The difference in speed is really huge. Thanks for the fix. lwalkowski |
1 | . It is ultimately the speed of these two use cases that will decide whether objectdb is worth the investment |
1 | it might be faster than JPA... ObjectDB has the same speed whether you use JPA or JDO. > I don't |
1 | limited to (say) 10 results. Is there any obvious way to speed up this querying? Taking minutes is not |
1 | Hi, after trying out objectdb for a while now and being quite impressed by its speed and overall performance I noticed a strange behaviour where an ORDER BY - directive isn't executed as it should be (and usually is, except in this special combination-case). Ordering seems to be ignored if we order |
1 | it terms of space and retrieval speed but may be more expansive in updates. See a recent forum thread |
1 | to a temporary file. Even without speed optimizations, but with priority on the memory usage. Ideally |
1 | would prefer to stick with embedded mode for the speed. Since we only have a single server |
