Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Test increasing the number of desisync instances #62

Closed
weaverba137 opened this issue Sep 26, 2024 · 1 comment
Closed

Test increasing the number of desisync instances #62

weaverba137 opened this issue Sep 26, 2024 · 1 comment
Assignees
@weaverba137

Comments

@weaverba137
Copy link
Member

Try increasing the scale of desisync instances in Spin.
@weaverba137 weaverba137 self-assigned this Sep 26, 2024
@weaverba137
Copy link
Member Author

As of 2024-10-23, with a scale of 3 on the rsync instances, Tucson mirror jobs are finishing in less than 24 hours, with the caveat that the hwtables directory is excluded, but this is a separate issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@weaverba137 weaverba137

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@weaverba137