objectdb on single server 20TB storage possible ?

Hi , i want to use objectdb on maximum 20TB of data.

It works fast on 20TB of data ? 

enough ?

Some people says objectdb fails beyond 128TB ?

(base) irdac1@gsrv5:~$ lscpu 
Architecture:             x86_64
  CPU op-mode(s):         32-bit, 64-bit
  Address sizes:          43 bits physical, 48 bits virtual
  Byte Order:             Little Endian
CPU(s):                   256
  On-line CPU(s) list:    0-255
Vendor ID:                AuthenticAMD
  Model name:             AMD EPYC 7H12 64-Core Processor
    CPU family:           23
    Model:                49
    Thread(s) per core:   2
    Core(s) per socket:   64
    Socket(s):            2
    Stepping:             0
    Frequency boost:      enabled
    CPU(s) scaling MHz:   58%
    CPU max MHz:          2600.0000
    CPU min MHz:          1500.0000
    BogoMIPS:             5190.40
    Flags:                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmper
                          f rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoex
                          t perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv
                          1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd amd_ppin arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold 
                          avic v_vmsave_vmload vgif v_spec_ctrl umip rdpid overflow_recov succor smca sev sev_es ibpb_exit_to_user
Virtualization features:  
  Virtualization:         AMD-V
Caches (sum of all):      
  L1d:                    4 MiB (128 instances)
  L1i:                    4 MiB (128 instances)
  L2:                     64 MiB (128 instances)
  L3:                     512 MiB (32 instances)
NUMA:                     
  NUMA node(s):           2
  NUMA node0 CPU(s):      0-63,128-191
  NUMA node1 CPU(s):      64-127,192-255
Vulnerabilities:          
  Gather data sampling:   Not affected
  Itlb multihit:          Not affected
  L1tf:                   Not affected
  Mds:                    Not affected
  Meltdown:               Not affected
  Mmio stale data:        Not affected
  Reg file data sampling: Not affected
  Retbleed:               Mitigation; untrained return thunk; SMT enabled with STIBP protection
  Spec rstack overflow:   Mitigation; Safe RET
  Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:             Mitigation; Retpolines; IBPB conditional; STIBP always-on; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected
  Srbds:                  Not affected
  Tsx async abort:        Not affected
  Vmscape:                Mitigation; IBPB before exit to userspace
(base) irdac1@gsrv5:~$ 

ObjectDB uses a single paged file for storage. By default, the page size is 2 KB, and the engine supports up to 2³¹ pages. With the maximum supported page size of 64 KB, a single database file can theoretically reach about 128 TB (64 KB × 2³¹ pages). This is a theoretical upper bound, not a guaranteed practical operating size.

In practice, performance and reliability depend much more on workload characteristics than on raw database size. Important factors include the number of concurrent users, transaction duration, query patterns, index usage, object sizes, and access locality. As database size grows, indexes become larger, memory pressure increases, recovery times get longer, and operational risk rises.

For multi-terabyte datasets, especially around 20 TB and above, it is strongly recommended to partition data across multiple databases (for example by time range or tenant). Whether ObjectDB is suitable at that scale depends on how the application behaves and is structured, rather than on a fixed size limit alone.