Significant performance difference using Wappler API Action (SC) over our existing non Wappler build (JSON API Call)

Hi Wappler team.

We are trying to move over a search interface to Wappler that uses an API that calls an Elastic Search service within AWS.

When we use this in our existing app - we are trying to replace with Wappler the call will take 1-2 seconds MAX for the most complex query, less than 0.5 second for simple queries. When we use the exact same API call can with Wappler it can take anywhere from 8 to 16 seconds.

Is this to be expected? Is there something we can do with this? This speed level will make it impossible for our existing end users.

Noting: I have tested this on the exact same staging server size on AWS as our staging environment for existing app. Exact same query to compare, and all permissions for accessing the ES api are correct (we secure by IP address).

Community Page
Last updated: