> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/writebackextreme/troubleshooting-and-faq/extension-errors/writebackextreme-appears-slow-when-performing-actions.md). # WriteBackExtreme appears slow when performing actions WriteBackExtreme appears slow when performing actions (e.g., Submitting data or loading tables) especially with Amazon Redshift or other cloud hosted databases: In many cases, slowness is caused by the performance of the underlying database rather than the extension itself. If the same SQL query that WriteBackExtreme executes also performs poorly when you run it directly in your database management tool, this confirms the bottleneck is in the database. To verify this, enable SQL logging for WriteBackExtreme through the advanced settings in the management console. Then run those same queries manually in your preferred database tool and compare the performance. If the queries are also slow outside of WriteBackExtreme, the issue is database-related. If they run quickly elsewhere but are slow only within WriteBackExtreme, please contact support and include your logs so we can help you resolve the issue. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.infotopics.com/writebackextreme/troubleshooting-and-faq/extension-errors/writebackextreme-appears-slow-when-performing-actions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.