Hi guys,
let me begin by saying I really like Pipedream, both the ethos and the product are great!
The only problem I’m having is extremely slow responses, I’m currently using a free plan to do some testing and my workflow just generates an hash from a piece of text and it’s taking 1s per request as shown in the network tab.
If I upgrade do you guarantee faster response time?
I would like to serve customers istantly (<100ms). If that’s not possible I need to have at least the guarantee of not exceeding 2s for whatever request from wherever location (obviously not taking into consideration the DB fetch time).
Is it possible to serve 100K users a day with Pipedream? Does it scale?
Post Scriptum:
Does Pipedream workflow retain global scoped variables from a call to the next?
Let’s say I put a constant declaration between the npm imports and the defineComponent export, do that constant persist?
Thanks,
Fredo
Hello @stopchemtrailsfred,
For the slow response,
I think you’re observing Pipedream cold start. If your workflow doesn’t process an event for roughly 5 minutes, Pipedream turns off the execution environment that runs your code. When your workflow receives another event, Pipedream creates a new execution environment and process your event. Initializing this environment takes a few seconds, which delays the execution of this first event . This is common on serverless platforms, and is typically referred to as a “cold start”.
You can refer to this document in order to understand how to solve it: Handling Cold Starts
Regarding serving 100K executions a day,
It’s possible with Pipedream, as Pipedream executes you workflow on AWS Lambda. Though the number of executions you can run depends on your plan and the number of credits/invocations you have. Visit https://pipedream.com/pricing for the latest pricing.
Regarding does Pipedream workflow retain global scoped variables from a call to the next?
You can use data exported by any steps in any other steps. All of the exported data from steps are read-only global variables. This video explain it quite clear. If you want to have writable global variables, you can use Pipedream data stores
Hi @vunguyenhung,
I’m sure that’s not cold start.
I’ve tried with many requests one after the other.
I checked out my DB and it’s very fast, dunno where things are going wrong, but I see that Pipedream events arrive fairly soon, the problem is that those seat with a spinner for quite a while (between 5s and 10s).
Maybe it’s the MongoDB connection process? Normally connection should be done just once in a regular backend, maybe that’s what’s slowing down the process.
Any idea on how to get a detailed explaination on where things might be slow?
If you have an idea just let me know.
Thanks,
Fredo
Hello @stopchemtrailsfred,
You can see the step execution time on your workflow deployed UI > Your action > Details as the image below
Since a day or two I’m getting this errors.
But the workflow executes just fine.
What should I do?
Thanks
Hello @stopchemtrailsfred,
I think it’s weird. In order for Pipedream support to check your case, could you access your Workflow settings and enable the option to allow Pipedream support to access your workflow?
Maybe @pierce can help to check when he comes online 
@pierce if you want we can have a meet, it would be a pleasure.
