Performance on Create a new thing

I have an API workflow that only does two things:

  1. Create a new thing
  2. Return data from API

During our performance tests, we are finding that this endpoint has an average response time of about 2500ms (2.5 seconds) which is unacceptable for such a simple operation.

I noticed that I was able to reduce the response time by removing the fields to update in the step for “Create a new thing”. We have about 30 fields that need to be populated on create, is there a better way to do this?

PS. The app is currently on the Personal plan.

1 Like

If you need to display the data on the front-end, you could call that separately and it’d appear almost instantly (probably a few hundred ms). Just a thought.

How would the client know what to retrieve when the unique id has not been sent back by the Create Workflow?

I also understand we are on one of the lowest tiers in terms of our plan, but surely it shouldn’t affect the performance this much especially when there is virtually nobody else using the app.

Use your free 2 units for one hour, and see how faster it is (in settings). Like you, my api workflow calls are very long and take between 10 to 20 seconds. When I boosted (test) with 40 credits, it took 2 seconds. That’s the good news :wink:

1 Like