add performance section to dev guide#10132
Merged
Merged
Conversation
Also cross-link related content.
sekmiller
reviewed
Dec 11, 2023
| Solr | ||
| ~~~~ | ||
|
|
||
| While in the past Solr performance hasn't been much of a concern, in recent years we've noticed performance problems when Harvard Dataverse is under load. We are investigating in `#9635 <https://github.com/IQSS/dataverse/issues/9635>`_. |
Contributor
There was a problem hiding this comment.
This issue is marked Closed as Completed
sekmiller
reviewed
Dec 11, 2023
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
|
||
| We'd like to scale Dataverse to better handle large number of files or versions (`#9763 <https://github.com/IQSS/dataverse/issues/9763>`_). | ||
|
|
Member
Author
There was a problem hiding this comment.
Good catch, in 80634c7 I linked to the PR as an example.
sekmiller
reviewed
Dec 11, 2023
| Learn from the Community How They Monitor Performance | ||
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
|
||
| Some members of the Dataverse community are likely users of newish tools like the ELK stack (Elasticsearch, Logstash, and Kibana), the TICK stack (Telegraph InfluxDB Chronograph and Kapacitor), GoAccess, Prometheus, Graphite, and more we haven't even heard of. In the :doc:`/admin/monitoring` section of the Admin Guide, we already encourage the community to share findings (, but we could dedicate time to this topic at our annual meeting or community calls. |
Member
Author
There was a problem hiding this comment.
Whoops. I removed the stray ( in 80634c7. Thanks.
sekmiller
reviewed
Dec 11, 2023
Contributor
sekmiller
left a comment
sekmiller
left a comment
There was a problem hiding this comment.
Looks Ok. A couple of the issues referred to are already closed as completed
sekmiller
approved these changes
Dec 12, 2023
Contributor
sekmiller
left a comment
sekmiller
left a comment
There was a problem hiding this comment.
Thanks for the updates
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
As explained in the issue, we'd like to capture our desired strategies in a document that we can review and revise for future use.
Which issue(s) this PR closes:
Special notes for your reviewer:
None. We went over the original doc at tech hours. This is mostly formatting it at rst.
Suggestions on how to test this:
Make sure the docs build.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No.
Is there a release notes update needed for this change?:
Hmm, I don't think so. Maybe an email to the mailing list.
Additional documentation:
It is documentation.