Internal Website Search

21-30 of 86 resultsRefresh

Query Execution on parallel threads don't lead to performance improvements

, it seems that time is spent on using temporary files. You may want to try increasing the configuration of the temporary file threshold, to reduce the use temporary files (although it may require more RAM). support Support

Pre-detach loading: retrieval by navigation not working in if statement

a temporary variable: test = lz.getPresent().getValue() != null & ... where it passes the if statement at all (because, for example, the temporary 'test' holder is used ... the test in a temporary variable: @Transient public Float

Possible issue with String fields

a regression bug (added in build 2.3.7_14) in handling temporary file path. Please try ... > When you increase the number of records in a transaction ObjectDB has to use temporary files. Even after a fix, it would be better if possible to avoid temporary file (to improve efficiency), e.g. by

Performance and memory usage of queries

file and deleting all the objects. ObjectDB uses temporary files for many operations (e.g. query processing) and should in future versions use temporary files also to enable very large

Optimistic Locking

>For example, if you retrieve an object, copy its data to a temporary data structure for presentation and then on update retrieves the object again and fills its with the data from the temporary data

Again about $temp from objectdb.conf

>   Sandu sandu Alexandru Constantinescu You can set the temporary ... .tmpdir" system property, but that will change the temporary directory for the entire JVM, not

500Mb ObjectDb database opening issue

another temporary database file). Try to load ObjectDB in the background (e.g. by opening a temporary database file as in the test above) and see if later it helps in speeding up the opening

ObjectDB 2.6.8

> Fixed a bug in using temporary files in large transactions. Reverts ... to fix a bug in using temporary files in large transactions.

again merger missing logs + objectdb exception

.7.2 (temporary stack traces in the log will be removed in the next build ... > hgzwicker Hans-Georg Zwicker The log entries in #28 above are temporary logging of the nested

An entityManager.flush() with many entities is not possible

amount of data requires using temporary files and the exception indicates a problem in using these files. Please check this forum thread. Maybe disabling deletion of temporary files