> For the complete documentation index, see [llms.txt](https://docs.movebot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.movebot.io/troubleshooting/performance-and-speed.md). # Performance and Speed Movebot has been built architecturally to be optimized for speed. In most cases, this means you will not need to make any adjustments to settings for your migration to perform quickly. There are however a few details that are useful to understand when trying to determine how quickly your migration will run. ### Rate-limiting For most migrations, rate-limiting is going to be the number #1 bottleneck. Rate-limiting is a mechanism used by API providers to prevent abuse and to limit the impact of buggy API consumer applications on other customers. Most cloud storage providers implement some level of rate-limiting and it's important to be aware of this as a limiter of your migration's performance. **Identifying rate-limiting** If your migration is being impacted by rate-limiting, it will be visible in the Performance Advisor graphs. The Performance Advisor provides a project-level summary of performance metrics. **What can be done about rate-limiting** Generally, we are at the mercy of the cloud platforms in terms of rate-limiting, but there are a few tricks with each platform if things are not progressing as quickly as you would like. If you believe rate-limiting has become a problematic bottleneck in your migration project, reach out to our team via and we can take a look at your project. ###
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.movebot.io/troubleshooting/performance-and-speed.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.