ObjectDB Database Search

Hello, we can't understand why the performance of queries is not the best and the execution requires so much memory. In the implementation of our UnitTests we have used "DELETE FROM Object" to delete the database. That did not work because we often get an "out of memory" exception

, it is supposed that the count of every field should be the same performance . I have no time to test

Hello, we have a performance problem when we use a large transaction. Let's do exactly the same in several transactions the ObjectDB works much faster. In our use case, we create many new entities and between the creations we call a select query. The execution of the query becomes slower at each

we have a customer system with 64 GByte RAM, 16 CPUs on 8 sockets, the fastest possible ssd. we wonder if the cache and other settings can be optimized to get the most performance these are the current settings, please advice what we could optimize hgzpincher Hans-Georg Zwicker

other useful hints for object db?  Performance is better, but still not the same 1000 ms in

Greetings ObjectDB team, The below questions assume a very large database (~1,000,000,000 objects): Q1: If my whole database is read only, is there a way to exploit this and optimize query performance ? Q2: Do LIKE operations have significant degradation on queries

we are fighting more or less since version 2.9 with the performance of our systems. We are completely unclear if indexes or statistics are really used.  sometimes a query like this takes takes around 500 ms, sometimes it takes 20 seconds  select distinct o from ObjectNode o join o

Hi, can someone share expirience with performance limits of ObjectDB especialy when quering tables with large records sets. Our issue is with tables with 100.000+ records. Everything was OK when we had few thousand records. We have a simple SELECT statement which selects from a table with 100.000

Hello, we have a question about a performance issue in a query. We executed a query on the following entity and there is only one entity in the database and we expects that the query is executed within 1 ms. SELECT v.sheetUID FROM TCVector But how you can see in the attached snapshot 'stacktrace

Performance issues on aggregate query

Low performance when getting grove roots

Performance of "InsertTest"

Help: After upgrading from 2.2.8_02 to 2.2.8_04, can't perform LIKE query

slow performance for a complex query

possible index required for improving query performance

we face performance issues on queries and therefore compared the times of 2 (same) databases, 2.9.0_05, one after adding statistics and one after additional doctor, here are the results: Query : select distinct o from ObjectNode o where (o.classIdentifier = '(RG)' and o.properties.name

Performance issue with query

log entry and massive performance issues

Monitoring and Performance counters

, the persistence provider must perform the automatic validation of entities. If no Bean Validation provider ... behavior. Since: Jakarta Persistence (JPA) 1.0 CALLBACK The persistence provider must perform the lifecycle ... . Since: Jakarta Persistence (JPA) 1.0 NONE The persistence provider must not perform lifecycle

( Class targetEntity ) Create a CriteriaDelete query object to perform a bulk delete operation ... query object to perform a bulk update operation. Parameters: targetEntity - target type for update

attribute, the persistence provider must also perform optimistic version checks when obtaining ... the database when pessimistic locking is performed . IllegalArgumentException - if the instance

and the entity contains a version attribute, the persistence provider must also perform optimistic version ... - if the entity does not exist in the database when pessimistic locking is performed . IllegalArgumentException

, the persistence provider must also perform optimistic version checks when obtaining the database ... not exist in the database when pessimistic locking is performed . IllegalArgumentException

is done via JTA, or it may be a resource-local entity manager, where transaction management is performed

Returns: selection item. Since: Jakarta Persistence (JPA) 1.0 Expression as ( Class type ) Perform

(JPA) 1.0 Expression as ( Class type ) Perform a typecast upon the expression, returning a new

Persistence (JPA) 1.0 Expression as ( Class type ) Perform a typecast upon the expression, returning

( Class type ) Perform a typecast upon the expression, returning a new expression object. Unlike

Expression as ( Class type ) Perform a typecast upon the expression, returning a new expression object

Expression as ( Class type ) Perform a typecast upon the expression, returning a new expression object

as ( Class type ) Perform a typecast upon the expression, returning a new expression object. Unlike

: selection item. Since: Jakarta Persistence (JPA) 1.0 Expression as ( Class type ) Perform a typecast

: selection item. Since: Jakarta Persistence (JPA) 1.0 Expression as ( Class type ) Perform a typecast

type ) Perform a typecast upon the expression, returning a new expression object. Unlike Expression

: selection item. Since: Jakarta Persistence (JPA) 1.0 Expression as ( Class type ) Perform a typecast

type ) Perform a typecast upon the expression, returning a new expression object. Unlike Expression

Jakarta Persistence (JPA) Interface jakarta.persistence.criteria.CriteriaUpdate Type Parameters: - the entity type that is the target of the update Super Interfaces: CommonAbstractCriteria The CriteriaUpdate interface defines functionality for performing bulk update operations using the Criteria

Persistence (JPA) 1.0 Expression as ( Class type ) Perform a typecast upon the expression, returning a new

: selection item. Since: Jakarta Persistence (JPA) 1.0 Expression as ( Class type ) Perform

Jakarta Persistence (JPA) Interface jakarta.persistence.criteria.CriteriaDelete Type Parameters: - the entity type that is the target of the DELETE Super Interfaces: CommonAbstractCriteria The CriteriaDelete interface defines functionality for performing bulk delete operations using the Criteria

: selection item. Since: Jakarta Persistence (JPA) 1.0 Expression as ( Class type ) Perform

. Since: Jakarta Persistence (JPA) 1.0 Expression as ( Class type ) Perform a typecast

as ( Class type ) Perform a typecast upon the expression, returning a new expression object. Unlike

required to perform any specific validation, so the semantics of this operation are entirely provider

_DATABASE_ACTION The action to be performed against the database. Standard actions

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder CriteriaUpdate createCriteriaUpdate (    Class targetEntity ) Create a CriteriaUpdate query object to perform a bulk update operation. Parameters: targetEntity - target type for update operation Returns: the query object. Since: Jakarta Persistence (JPA) 2.1

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder CriteriaDelete createCriteriaDelete (    Class targetEntity ) Create a CriteriaDelete query object to perform a bulk delete operation. Parameters: targetEntity - target type for delete operation Returns: the query object. Since: Jakarta Persistence (JPA) 2.1

Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.ValidationMode CALLBACK The persistence provider must perform the lifecycle event validation. It is an error if there is no Bean Validation provider present in the environment. Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Enum Constant in jakarta.persistence.ValidationMode NONE The persistence provider must not perform lifecycle event validation. Since: Jakarta Persistence (JPA) 1.0