Dataverse native api performance

27 views
Skip to first unread message

Michel Bamouni

unread,
Apr 26, 2018, 8:50:24 AM4/26/18
to Dataverse Users Community
Hello,

After upgrade from dataverse 4.5.1 to dataverse 4.6.2, I observe native api performance degradation. A curl request to create take 2 minutes.
How can solve this?

best regards,

Michel

Philip Durbin

unread,
Apr 26, 2018, 8:57:03 AM4/26/18
to dataverse...@googlegroups.com
2 minutes! Can you please put more specifics into a new issue at https://github.com/IQSS/dataverse/issues ? Thanks!

--
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-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/24bf2f89-9508-41d4-bb08-ce195d09c22e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

Michel Bamouni

unread,
Apr 27, 2018, 9:04:31 AM4/27/18
to Dataverse Users Community
Hi,

After profiling dataverse stack trace, I find the cause of my problem.
This was due to the communication between dataverse and datacite.

Thanks Phil for your answer

Michel



Le jeudi 26 avril 2018 14:57:03 UTC+2, Philip Durbin a écrit :
2 minutes! Can you please put more specifics into a new issue at https://github.com/IQSS/dataverse/issues ? Thanks!
On Thu, Apr 26, 2018 at 8:50 AM, Michel Bamouni <olimi...@gmail.com> wrote:
Hello,

After upgrade from dataverse 4.5.1 to dataverse 4.6.2, I observe native api performance degradation. A curl request to create take 2 minutes.
How can solve this?

best regards,

Michel

--
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-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.

Philip Durbin

unread,
Apr 27, 2018, 10:12:13 AM4/27/18
to dataverse...@googlegroups.com
Thanks for the update! I just closed https://github.com/IQSS/dataverse/issues/4624

For the record, communication with DataCite should be centralized, so I assume you would have seen performance problems with similar operations in the web interface.

On Fri, Apr 27, 2018 at 9:04 AM, Michel Bamouni <olimi...@gmail.com> wrote:
Hi,

After profiling dataverse stack trace, I find the cause of my problem.
This was due to the communication between dataverse and datacite.

Thanks Phil for your answer

Michel


Le jeudi 26 avril 2018 14:57:03 UTC+2, Philip Durbin a écrit :
2 minutes! Can you please put more specifics into a new issue at https://github.com/IQSS/dataverse/issues ? Thanks!
On Thu, Apr 26, 2018 at 8:50 AM, Michel Bamouni <olimi...@gmail.com> wrote:
Hello,

After upgrade from dataverse 4.5.1 to dataverse 4.6.2, I observe native api performance degradation. A curl request to create take 2 minutes.
How can solve this?

best regards,

Michel

--
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-community+unsubscribe...@googlegroups.com.

--
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-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse-community@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/10ab05c6-b638-4869-a45d-281b1de4f4b5%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages