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
How to reduce time to migrate data from rdb file to redis cluster ? #719
Comments
你是否使用 |
In shake.toml function is |
源端是 standalone 的情况下没有办法进一步提高速度。但一小时的同步时间远超我的测试结果,请提供一下运行日志,可以帮助分析一下性能瓶颈。 |
logs from the last time I ran with pipeline_count_limit as 8196. @suxb201
|
@suxb201 one more thing, I have observed is sometimes when I get errors like below |
@suxb201 请问有哪些办法可以帮助我提高同步速度呢,比如分布式并发同步之类的? 谢谢 |
@dhruvil-alphonso 速度是:read_ops=[56226.66],已经很快了,你的 key 很多是吗? @xishian 是的,现在只有一个 client 在写,只能提供 6 万左右的写能力。我后面打算改成多个 client,并按 key 并发来提高写能力。 |
Yes, I have lots of keys @suxb201, around 144M or so . Looking forward to the multiple clients support. When do you plan to release that ? |
@dhruvil-alphonso 需要很多改动。本周或者下周。 |
@dhruvil-alphonso 我认为我的修改不能提高你的同步速度。需要再进一步确认你的瓶颈在哪里。可能是从盘上读取文件较慢,可能是 dump.rdb 文件解析较慢,也可能是目的端消费命令较慢。 |
问题描述(Issue Description)
Looking for ways optimize the calls and reduce time it takes to migrate data from rdb file to redis cluster. Right now, it is taking about an hour to ingest a 10GB rdb file into a cluster. I have only tuned the
pipeline_count_limit = 4096
, and can do it further to some large number, but would like to get suggestions on how i can reduce this to a significantly smaller number. Any help would be helpful. The command I am executing is./redis-shake shake.toml
请在这里简要描述你遇到的问题。
Please provide a brief description of the issue you encountered.
Apart from the reader/writer config, this is the rest of toml file
环境信息(Environment)
日志信息(Logs)
如果有错误日志或其他相关日志,请在这里提供。
If there are any error logs or other relevant logs, please provide them here.
其他信息(Additional Information)
请提供任何其他相关的信息,如配置文件、错误信息或截图等。
Please provide any additional information, such as configuration files, error messages, or screenshots.
The text was updated successfully, but these errors were encountered: