Dear Arcade Team,

this is not really a bug but a request for some insights. We don't really now how to tune arcadedb for larger workloads. We have a RAG applicaiton with about 50-100 GB of Data. Longer search times to 30-60 Seconds are acceptable, so we don't plan to load the full data into RAM.

We are running arcadedb in embedded mode and don't know how much RAM we should allocate for the container, How much we should reserve for heap. If we should use any tuning flags of arcadedb (e.g. ARCADEDB_OPTS_MEMORY).

Any hint would be apreachiated.

Thank you