Internal Website Search

- Source code - Netbeans profiler traces (seems issue in createEntityManager() performance ) duskov ... ! I am on OSX 10.12.6, JVM 1.8.0_144-b01, and I was also having performance issues

When populating a large database (10s of GBs) performance drops suddenly at a certain time whenever I run the populating application.  Is there typically a database size when indexes ... , regardless of the JVM heap size and the ObjectDB cache size). Except this, ObjectDB performance should not

to see considerable degrade in performance caused internal objectdb locking: "pdncrttorfo42-WSAgent-1 ... if we perform an upgrade is it backwards compatible with old version of files e.g thoes with different

Hello guys, i have a question regarding "objectdb.java.util.ArrayList" and performance . In my project i'm iterating over an array with about 100k items. Fetching them into the EntityManager takes ... this iteration. Can anybody give me a hint whats the reason or how i can increase performance here? ph

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

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

provider must perform optimistic version checks when obtaining the database lock. If these checks fail ... type is pessimistic and the entity has a version attribute, the persistence provider must perform ... , the persistence provider must also perform optimistic version checks when obtaining the database lock

must perform the automatic validation of entities. If no Bean Validation provider is present in ... .0 CALLBACK The persistence provider must perform the lifecycle event validation. It is an error ... provider must not perform lifecycle event validation. Since: JPA 2.0 Public Static Enum Methods

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

attribute, the persistence provider must also perform optimistic version checks when obtaining ... locking is performed OptimisticLockException - if the optimistic version check fails

and the entity contains a version attribute, the persistence provider must also perform optimistic version ... locking is performed OptimisticLockException - if the optimistic version check fails

JPA Interface 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 API Criteria API bulk delete operations map directly

JPA Annotation Version Target: METHOD, FIELD Implemented Interfaces: Annotation Specifies the version field or property of an entity class that serves as its optimistic lock value. The version is used to ensure integrity when performing the merge operation and for optimistic concurrency control

JPA Method in javax.persistence.criteria.Expression Expression as (   Class  type ) Perform a typecast upon the expression, returning a new expression object. This method does not cause type conversion: the runtime type is not changed. Warning: may result in a runtime failure

JPA Enum Constant in javax.persistence.ValidationMode NONE The persistence provider must not perform lifecycle event validation. Since: JPA 2.0

JPA Enum Constant in javax.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: JPA 2.0

JPA Enum Constant in javax.persistence.ValidationMode AUTO If a Bean Validation provider is present in the environment, the persistence provider must perform the automatic validation of entities. If no Bean Validation provider is present in the environment, no lifecycle event validation takes place. This is the default behavior. Since: JPA 2.0

JPA Interface Expression Type Parameters: - the type of the expression Super Interfaces: Selection , TupleElement Type for query expressions. Since: JPA 2.0 The JPA Query Expressions (JPQL / Criteria) article explains how to use Expression . Public Methods Expression as (Class  type) Perform

JPA Interface ParameterExpression Type Parameters: - the type of the parameter expression Super Interfaces: Expression , Parameter , Selection , TupleElement Type of criteria query parameter expressions. Since: JPA 2.0 Public Methods Expression as (Class  type) Perform a typecast

is pessimistic and the entity has a version attribute, the persistence provider must perform optimistic

otherwise. Since: JPA 2.0 Public Methods Expression as (Class  type) Perform a typecast upon the expression

has a version attribute, the persistence provider must perform optimistic version checks

that are common to the parent class, and a join is performed to instantiate the subclass. Since: JPA 1.0

JPA Enum Constant in javax.persistence.InheritanceType JOINED A strategy in which fields that are specific to a subclass are mapped to a separate table than the fields that are common to the parent class, and a join is performed to instantiate the subclass. Since: JPA 1.0

JPA Method in javax.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 Return: the query object Since: JPA 2.1

. Since: JPA 2.0 Public Methods Expression as (Class  type) Perform a typecast

classes and to perform common operations needed by implementations, not by end users. JDOImplHelper ... for JDOPermission("setStateManager"). To improve performance , first the set of authorized classes ... loader as the PersistenceCapable class performing the registration. Parameters: pcClass

a performance optimization as an alternative to using reflection to construct a new instance. It is used ... is used as a performance optimization as an alternative to using reflection to construct a new instance

the PersistenceCapable class performing the registration. Parameters: pcClass - the PersistenceCapable class used as

JDO Method in javax.jdo.PersistenceManagerFactory void setReadOnly (   boolean flag ) Sets the value for whether the datastore is to be considered read-only. ReadOnly set to false specifies that no updates can be performed to the datastore, and if updates are attempted

for JDOPermission("setStateManager"). To improve performance , first the set of authorized classes

set to false specifies that no updates can be performed to the datastore, and if updates

performing any action on any persistent instance that might require the JDO implementation to use

JDO Method in javax.jdo.datastore.JDOConnection void close () Returns this connection to the JDO implementation. The object must be returned to the JDO implementation prior to calling any JDO method or performing any action on any persistent instance that might require the JDO implementation