Slow response when invoking the Edit Metadata page

[edwin law]

Hi everyone

We notice that the response time to enter the Edit Metadata page is longer (around 11 seconds) than before. Below are some facts about our on-premises Dataverse installation:

- version: 6.8 build 1994-92d1ec8

- No. of folders/dataverses: 71

- No. of datasets: 87

- Solr version: 9.8.0

- PostgreSQL version: 16.11

- RHEL version: 9.7

- Payara Glassfish: 6.2025.3

- CPU: 2.8 GHz vCPU x 4

- RAM: 16 GB

Is the response time (11 seconds) much longer than normal/average Dataverse platforms? If so, any tips for identifying the bottlenecks and applying remedial actions? Many thanks!

Best regards

Edwin

[Philip Durbin]

Hi Edwin,

I wish I had a quick fix for you. No, that 11 seconds doesn't sound normal to me. It sounds quite slow.

In development I've used tools like VisualVM to try to figure out where the bottleneck is. From what I understand, it's possible to use profilers like this in production as well. We have a related page here but nothing about profilers: https://guides.dataverse.org/en/6.11/admin/monitoring.html

Another stat I'm curious about is the amount and percentage of heap space allocated to the JVM. Don and Leonid know a lot about this. Let me at least post some links to some relevant discussions:

- https://groups.google.com/g/dataverse-community/c/1zW8AvkZP1o/m/sHrOvQYaKgAJ

- https://groups.google.com/g/dataverse-community/c/RsOHly2A_IE/m/0hT3z79JCAAJ

I hope this helps!

Phil

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/1dee7fbe-09de-4c04-b6e8-88b8ffdcb2d2n%40googlegroups.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[edwin law]

Hi Philip

Thanks so much for your tips. Our current allocations of RAM to the JVM are as follows:

        <jvm-options>-Xmx7992m</jvm-options>
        <jvm-options>-Xms7992m</jvm-options>

Moreover, we have added the following Solr settings according to Dataverse's suggestions (https://guides.dataverse.org/en/latest/developers/performance.html#performance) 

      <system-property name="dataverse.feature.avoid-expensive-solr-join" value="true"></system-property>
      <system-property name="dataverse.feature.add-publicobject-solr-field" value="true"></system-property>
      <system-property name="dataverse.feature.reduce-solr-deletes" value="true"></system-property>

The hardware usage seems normal:

Is the problem related to our customized metadata blocks (the Citation metadata block and the other specific to our institution)? Thanks.

Best regards

Edwin

[James Myers]

A timely question – I’ve been looking into this and finally created a PR (#12617) that switches to a different widget for the ~8000 entry language metadata field. In my testing, that was slowing loading by many seconds (for me - ~20 seconds on demo.dataverse.org versus 2-3 on data.stage.qdr.org where I’ve deployed the PR for testing at QDR). Unless there’s something else going on, I think this would have appeared as of 6.4 when the language field started supporting ISO 639-3 with many more language codes. I’m surprised there haven’t been more reports – it probably depends on browser performance.

 

Since the new approach uses some server-side logic, it doesn’t help with older versions (unless someone patches them), so the best work-around for older versions might be to avoid switching to using all the new language codes. (I haven’t looked at the citation metadatablock changes for this – I’m guessing you’d want to update the language entries from v6.3 to their equivalents in 6.4+ but you could skip/delete the ones you don’t need. – Happy to discuss offline if that’s something people plan to do).

 

-- Jim

 

From: dataverse...@googlegroups.com <dataverse...@googlegroups.com> On Behalf Of edwin law
Sent: Thursday, August 13, 2026 11:33 PM
To: Dataverse Users Community <dataverse...@googlegroups.com>
Subject: Re: [Dataverse-Users] Slow response when invoking the Edit Metadata page

 

Hi Philip

 

Thanks so much for your tips. Our current allocations of RAM to the JVM are as follows:

 

        <jvm-options>-Xmx7992m</jvm-options>
        <jvm-options>-Xms7992m</jvm-options>

 

Moreover, we have added the following Solr settings according to Dataverse's suggestions (https://guides.dataverse.org/en/latest/developers/performance.html#performance) 

 

      <system-property name="dataverse.feature.avoid-expensive-solr-join" value="true"></system-property>
      <system-property name="dataverse.feature.add-publicobject-solr-field" value="true"></system-property>
      <system-property name="dataverse.feature.reduce-solr-deletes" value="true"></system-property>

The hardware usage seems normal:

 

Best regards

Edwin

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/1dee7fbe-09de-4c04-b6e8-88b8ffdcb2d2n%40googlegroups.com.

 

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/882fc8c3-43de-465e-861a-0125f1e268a3n%40googlegroups.com.

[Kirill Batyuk]

Hi Edwin,

My first line of defense is to restart the server. Looking at your top command, the server has not been restarted in almost a year. In any case, if it doesn’t fix it, it should not hurt anything.

-Kirill.

 

 

Kirill Batyuk

Systems Librarian

MBLWHOI Library

Data Library and Archives

Woods Hole Oceanographic Institution

508-289-2850

kba...@whoi.edu

mblwhoilibrary.org -- whoi.edu

 

 

 

From: dataverse...@googlegroups.com <dataverse...@googlegroups.com> On Behalf Of James Myers
Sent: Friday, August 14, 2026 2:24 PM
To: dataverse...@googlegroups.com
Subject: [EXTERNAL] RE: [Dataverse-Users] Slow response when invoking the Edit Metadata page

 

This email originated outside of WHOI. Please use caution if clicking on links or opening attachments.

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/DM6PR07MB6252143EA5699D7106AFAA78BFDA2%40DM6PR07MB6252.namprd07.prod.outlook.com.

[edwin law]

Hi Kirill

Many thanks for the suggestion. We will schedule regular restarts of our server to keep it robust.

Best regards

Edwin

[edwin law]

Hi Jim

Many thanks for sharing your solution for fixing the slow response issue. We removed 7800+ unnecessary controlled-vocabulary entries from the language field of the Citation Metadata block, both in the database tables "controlledvocabalternate" & "controlledvocabularvalue" and in the citation.properties file. After that, the loading time has been greatly reduced to within 1 second. 

Best regards

Edwin