-
Notifications
You must be signed in to change notification settings - Fork 51
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.
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
[DOCS]: Timing on backup/restore #547
Comments
We don’t have official benchmarking documentation for backup and restore latency. The time required mainly depends on object storage performance and Milvus’s processing capability. Perhaps it would be more helpful if the backup tool provided progress tracking and estimated time remaining. Would that better suit your needs? |
Progress tracking and time estimation would be helpful! Thanks.
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: huanghaoyuanhhy ***@***.***>
Sent: Tuesday, February 18, 2025 10:40:31 PM
To: zilliztech/milvus-backup ***@***.***>
Cc: Isabelle Francke ***@***.***>; Author ***@***.***>
Subject: Re: [zilliztech/milvus-backup] [DOCS]: Timing on backup/restore (Issue #547)
We don’t have official benchmarking documentation for backup and restore latency. The time required mainly depends on object storage performance and Milvus’s processing capability.
Perhaps it would be more helpful if the backup tool provided progress tracking and estimated time remaining. Would that better suit your needs?
—
Reply to this email directly, view it on GitHub<#547 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BODG7DZSMNFEA7INZV2SDDT2QP4K7AVCNFSM6AAAAABXMJRQXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRXGQZTGNRRGY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
[huanghaoyuanhhy]huanghaoyuanhhy left a comment (zilliztech/milvus-backup#547)<#547 (comment)>
We don’t have official benchmarking documentation for backup and restore latency. The time required mainly depends on object storage performance and Milvus’s processing capability.
Perhaps it would be more helpful if the backup tool provided progress tracking and estimated time remaining. Would that better suit your needs?
—
Reply to this email directly, view it on GitHub<#547 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BODG7DZSMNFEA7INZV2SDDT2QP4K7AVCNFSM6AAAAABXMJRQXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRXGQZTGNRRGY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
/assign |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Documentation Link
No response
Describe the problem
Hi, wondering if there is any documentation on latency related to creating and restoring backups. From personal experience I have noticed that all commands take significantly longer the more backups that are created.
Is there any documented latency benchmarking?
Describe the improvement
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: