add tips to reduce latency

Author: andrewjschuang

docs-v2/pages/troubleshooting.mdx

@@ -246,6 +246,18 @@ Pipedream also operates a [built-in key-value store](/data-stores/) that you can
 
 Use Pipedream's [built-in Delay actions](/workflows/flow-control/#delay) to delay a workflow at any step.
 
+### How can my workflow run faster?
+
+Here are a few things that can help your workflow execute faster:
+
+1. **Increase Memory Allocation:** [Increase your workflow memory](/workflows/settings#memory) to at least 512 MB. Raising the memory limit will proportionally increase CPU resources, leading to improved performance and reduced latency.
+
+2. **Return Static HTTP Responses:** If your workflow is triggered by an HTTP source, [return a static HTTP response](/workflows/triggers#http-responses) directly from the trigger configuration. This ensures the HTTP response is sent to the caller immediately, before the rest of the workflow steps are executed.
+
+3. **Simplify Your Workflow:** Reduce the number of steps and [segments](/workflows/control-flow#workflow-segments) in your workflow. This lowers the overhead involved in managing step execution and exports.
+
+4. **Activate Warm Workers:** Use and increase the number of dedicated workers to [eliminate cold starts](/workflows/settings#eliminate-cold-starts), ensuring your workflow is ready to execute immediately.
+
 ### How can I save common functions as steps?
 
 You can create your own custom triggers and actions ("components") on Pipedream using [the Component API](/components/api/). These components are private to your account and can be used in any workflow.

docs-v2/pages/workflows/settings.mdx

@@ -112,6 +112,14 @@ By default, workflows run with {process.env.MEMORY_LIMIT} of memory. If you're p
 
 Increasing your workflow's memory gives you a proportional increase in CPU, so increasing your workflow's memory can reduce its overall runtime and make it more performant.
 
+<Callout type="info">
+**Reducing Workflow Latency**
+
+To reduce latency from the trigger to the end of your workflow, consider increasing the memory allocation to at least 512MB. This will result in significantly better performance compared to the default 256MB.
+For other ways to improve your workflow's performance, see [Troubleshooting](/troubleshooting#how-can-my-workflow-run-faster).
+
+</Callout>
+
 **Pipedream charges credits proportional to your memory configuration**. When you modify your memory settings, Pipedream will show you the number of credits you'll be charged per execution. [Read more here](/pricing/#how-does-workflow-memory-affect-credits).
 
 ### Concurrency and Throttling

docs-v2/pages/workflows/triggers.mdx

@@ -195,7 +195,7 @@ import got from "got";
 export default defineComponent({
   async run({ steps, $ }) {
     const pipeline = promisify(stream.pipeline);
-    
+
     await pipeline(
       got.stream(steps.trigger.event.body.raw_body_url),
       fs.createWriteStream(`/tmp/raw_body`)
@@ -295,6 +295,14 @@ By default, when you send a [valid HTTP request](#valid-requests) to your endpoi
 
 When you're processing HTTP requests, you often don't need to issue any special response to the client. We issue this default response so you don't have to write any code to do it yourself.
 
+
+<Callout type="info">
+**Reducing Workflow Latency**
+
+To reduce latency for HTTP requests, return a static response directly from the trigger configuration. This ensures the HTTP response is sent to the caller immediately, before the rest of the workflow steps are executed. For more information, see [Sources](https://pipedream.com/docs/sources).
+
+</Callout>
+
 #### Customizing the HTTP response
 
 If you need to issue a custom HTTP response from a workflow, you can either: