 1 | attachments in ObjectDB as byte[] fields. The database size is limited to 128 TB (= 131,072 GB = 134,217,728 MB). There is no limit on object sizes, but byte[] is limited by Java to 2GB |
1 | MyEntity {
@GeneratedValue @Id long id;
@Index int value;
byte[] data = new byte[1500];
}
} Your observation is correct. There is a fetch optimization that collects |
1 | baURI is a byte[];
JP QL> select e.baURI.length from URI e where id=82778
JP QL> [ObjectDB 2.2.9_04] javax.persistence.PersistenceException
Navigation from 'byte[]' through 'length' is invalid (error 763)
at com.objectdb.jpa.JpaQuery.getResultList(JpaQuery.java:636)
at util.JPQLcmd.QureyCMD |
1 | (Bytes) MyEntity 200.000 10.400.000 char[] 7.154 ... Memory (Bytes) char[] 807.363 13.237.950 String 807.291 |
1 | #instances #bytes class name
----------------------------------------------
1 ... #bytes class name
----------------------------------------------
1: 704422 |
1 | ())
{
NetworkInterface ni = (NetworkInterface)e.nextElement();
byte ... ();
byte[] hardwareAddress = ni.getHardwareAddress();
System.out.println(indent |
1 | ? Could you please provide more details about the byte[] allocations? Who holds them? What is the common size of the byte[] that fills the heap? How many instances of this size exist? I can send |
1 | .Launcher$AppClassLoader @ 0x853f0440" occupies 375,301,672 (17.92%) bytes. The memory is accumulated ... $AppClassLoader @ 0x853f0440" occupy 1,436,097,296 (68.58%) bytes. These instances are referenced from |
1 | ;
byte[] data = new byte[512];
public MyEntity(int x) {
this.x = x |
1 | list; } The 2nd level cache stores object data (byte[]) rather than live entity objects ... cache as object IDs (PK) encoded in the byte[] of a MyEntity1 instance. When you retrieve a MyEntity1 |