在AWS Lambda上使用bcrypt超时问题

I'm making a web app using AWS lambda. Everything is working great and my cold start requests are under 200ms. Go has absolutely blazing speed. But there is an issue with user registration and auth.

Computing a bcrypt hash takes 19 seconds with 128 mb of reserved memory. Increasing the memory does take the request time down but increases the cost per transaction.

For only two of my calls needing the increased space this seems pretty wasteful. I'm considering making a separate endpoint for just auth. They share a DB so would not matter to much.

Is there a better way? Different auth scheme? Different infrastructure?