Bethany Seeger (Jan 09 2025 at 19:07): Bethany Seeger (Jan 09 2025 at 19:07):Hi,
I see the great information about Harvard's system setup for Dataverse system in the guide[1]. I was wondering if anyone had a recommendation for the Java Opts -Xmx setting? I think ours is currently too low and we're hitting issues maxing out the heap memory, but I'm not sure what a good setting for that would be relative to the overall memory the machine has.
Any thoughts welcome.
Thanks!
Bethany
[1]https://guides.dataverse.org/en/latest/installation/prep.html
Don Sizemore (Jan 15 2025 at 16:05):Hello,
I tried to reply to you last week but was unable to send in Zulip. Our integration testing runs in a single VM with 8GB of RAM with a 4GB JVM heap (Xmx) as a functional minimum. The current PrimeFaces front-end consumes 10MB of memory for each session (authenticated or not) and tabular ingest can consume up to 10 times the filesize in RAM, depending on the format. UNC Dataverse, for reference, runs in a VM with 64GB of RAM and a 48GB JVM heap. With heavy caching we routinely max that out.
I hope this helps?
Don
Bethany Seeger (Jan 15 2025 at 20:39):Thanks, Don, this is very helpful.
Hi Don,
Thank you - this information helps a lot!
I think we were running way low for what we needed. We had given the JVM 3.8 GB for the heap but just upped that to 8GB for the HEAP and 32GB for the system in total. I suspect we need to up the heap value more, as I'm not sure how well this will handle under load.
That's really good to know about the TAB ingest. We had a user upload about 1000 small CSV files (in one zip) that got converted to TAB - it took our server down with all the processing. Eventually I just had them upload it via direct upload as zip files instead. They were content with that and didn't want the TAB files anyways.
Best,
Bethany
Last updated: Oct 30 2025 at 05:14 UTC