> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/tutorials/video-tutorials.md). # Video Tutorials ### Technology Behind Performance Learn in this video about how to boost the performance of your wem applications. Gijs Reijner talks you through the technical aspects regarding performance. For a lot of cases this is because of filter expressions, and can be resolved with a more knowledge about how filter expressions work. {% embed url="" %} ### Filter Queries and Batch Processing In this video Ralph Coesmans talks about Filter queries and Batch Processing. Filter queries can often be a cause for an application to feel slow, and can be improved with the use of proper filter queries. When you need to update many rows in a list batch processing can be strategy to keep it fast and efficient. {% embed url="" %} ### The Double Loop Douwe Roelofsen talks you trough why and how the double loop can make your application faster. Replacing the Go To Row with a double loop limits the amount of queries your application has to perform. He also talks about Identifying the cause of a possible slowdown, and highlights the usual suspects that slow a application down. {% embed url="" %} --- # 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.wem.io/platform/tutorials/video-tutorials.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.