Stream: community

Topic: Dataverse Production Performance

view this post on Zulip Marcos Anjos (Apr 01 2024 at 15:21):

I'm facing an issue in the production Dataverse environment. Every time I load a dataset, the application goes offline. I've noticed spikes in RAM memory consumption during these instances. However, manually restarting the services restores operability.
Could anyone help me or has anyone experienced something similar? What steps should be taken? Note: I've already upgraded the RAM from 8GB to 10GB (did not resolve the issue).
WhatsApp-Image-2024-04-01-at-11.46.45_3ec349d9.jpg

view this post on Zulip Philip Durbin 🚀 (Apr 01 2024 at 15:34):

Sorry to hear. What version of Dataverse are you running?

view this post on Zulip Philip Durbin 🚀 (Apr 01 2024 at 15:35):

And does this happen with every dataset, even small ones?

view this post on Zulip Philip Durbin 🚀 (Apr 01 2024 at 15:39):

By small I mean datasets with only a few files and a few versions.

view this post on Zulip Marcos Anjos (Apr 01 2024 at 15:46):

Philip Durbin said:

Sorry to hear. What version of Dataverse are you running?

I'm using version 5.12.1. Yes, for any dataset size.

view this post on Zulip Philip Durbin 🚀 (Apr 01 2024 at 15:47):

Something seems seriously wrong. Anything in server.log?

view this post on Zulip Marcos Anjos (Apr 01 2024 at 15:49):

@Philip Durbin Even if I only add metadata (whether or not loading any files) and save, the application crashes.

view this post on Zulip Marcos Anjos (Apr 01 2024 at 15:50):

Philip Durbin said:

Something seems seriously wrong. Anything in server.log?

I will check

view this post on Zulip Philip Durbin 🚀 (Apr 01 2024 at 15:51):

How long were you in production before this started happening? The map says 2023.

view this post on Zulip Marcos Anjos (Apr 01 2024 at 15:54):

Philip Durbin said:

How long were you in production before this started happening? The map says 2023.

This problem started about 3 weeks ago, and it seems the application crashes every weekend. However, last week, this same issue occurred four times in a row.

view this post on Zulip Philip Durbin 🚀 (Apr 01 2024 at 15:56):

Did anything change three weeks ago? Maybe an upgrade?

view this post on Zulip Oliver Bertuch (Apr 01 2024 at 17:42):

Is this a classic or a containerized install?

view this post on Zulip Oliver Bertuch (Apr 01 2024 at 17:43):

When you raised the memory, did you also apply new limits to heap and other JVM memory config options?

view this post on Zulip Oliver Bertuch (Apr 01 2024 at 17:44):

I suppose you're using JRE 11 with 5.12.1. Upgrading to 6+ would give you JRE 17 with more recent and faster GC methods you could try as well.

Last updated: Nov 01 2025 at 14:11 UTC