Performance Issues with Lambda Functions

Hello,

I'm reaching out to the forum regarding an issue I recently encountered.

We are developing a stock management application. During the development phase, everything was working fine because we were handling approximately 1,000 product references (i.e., 1,000 rows in the Reference table, which contains around 40 columns).

However, since moving to production, this table now contains 40,000 rows, and most of the Lambda functions I created can no longer handle the load. They often fail with the error "Connection lost... Reconnecting" and sometimes with "Unknown error."

To illustrate my issue, here’s a concrete example:
I have a Lambda function that takes the entire Reference table as input using "Query all records from". This function is responsible for:

  • Cleaning text,

  • Formatting dates,

  • Creating two separate lists,

  • Performing calculations on these lists,

  • Generating file names.

These processed data are then used in another function that generates two CSV files and compresses them into a ZIP archive.

However, since the table grew to 40,000 rows, this Lambda function no longer works. Many other similar functions are also affected.

I have tried several solutions:

  • Splitting the function into smaller parts,

  • Moving it into a separate function,

  • Running it as a background task…

Unfortunately, none of these solutions have worked. Right now, the only viable option I see is to rewrite these Lambda functions in native Xano.

For context, we were on the Launch plan and have since upgraded to Scale 1x.

Do you have any alternative solutions to suggest?

Thanks in advance for your help!

1
2 replies