I put a real search engine into a Lambda, so you only pay when you search
nixiesearch.substack.com
I put a real search engine into a Lambda, so you only pay when you search
1–10 of 15 posts
Re: I put a real search engine into a Lambda, so you only pay when you search
#2"128MB default with up to 3008MB max. You can submit a support ticket to get 10GB RAM, but I was too lazy to argue with AWS support."
Was this written before wide availability of 10g memory lambdas?
Re: I put a real search engine into a Lambda, so you only pay when you search
#3"128MB default with up to 3008MB max. You can submit a support ticket to get 10GB RAM, but I was too lazy to argue with AWS support." Was this written before wide availability of 10g memory lambdas?
Surprisingly, 3GB is a real practical RAM limit for aws lambdas in 2025: you can only have more than that if you submit a support ticket. But it's not really mentioned anywhere in the docs.
Re: I put a real search engine into a Lambda, so you only pay when you search
#4This is great!
I have been using Quickwit as a low cost search engine on Lambda. It works very well for my relatively small and infrequently updated dataset.
Unfortunately Quickwit devs have decided to not support the Lambda deployment mode going forward so eventually I'll need another option.
Re: I put a real search engine into a Lambda, so you only pay when you search
#5"128MB default with up to 3008MB max. You can submit a support ticket to get 10GB RAM, but I was too lazy to argue with AWS support." Was this written before wide availability of 10g memory lambdas?
Surprisingly, 3GB is a real practical RAM limit for aws lambdas in 2025: you can only have more than that if you submit a support ticket. But it's not really mentioned anywhere in the docs.
https://aws.amazon.com/about-aws/whats-new/2020/12/aws-lambd...
Is what you're talking about a new thing? Or respectfully, are you just wrong?
Re: I put a real search engine into a Lambda, so you only pay when you search
#6"128MB default with up to 3008MB max. You can submit a support ticket to get 10GB RAM, but I was too lazy to argue with AWS support." Was this written before wide availability of 10g memory lambdas?
Surprisingly, 3GB is a real practical RAM limit for aws lambdas in 2025: you can only have more than that if you submit a support ticket. But it's not really mentioned anywhere in the docs.
https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-...
The default Lambda quota for all accounts is 10240 MB. I've never seen it below that (in recent memory, at least), even on fresh accounts not connected to a big org.
I know I routinely use 10gb of RAM for my account that's never talked to support for the related CPU allocation.
Re: I put a real search engine into a Lambda, so you only pay when you search
#7Fascinating. In a modern app I find that search quickly can become one of the most expensive aspects. It’s not trivial to implement on your own and with the growing effort on hybrid style search, the costs continue to grow. I love work like this.
Re: I put a real search engine into a Lambda, so you only pay when you search
#8Maybe a stupid question: why can't the indexer write directly to EFS, why does it write to s3 and lambda downloads it to EFS?
Re: I put a real search engine into a Lambda, so you only pay when you search
#9Earlier quoted context omitted.
Surprisingly, 3GB is a real practical RAM limit for aws lambdas in 2025: you can only have more than that if you submit a support ticket. But it's not really mentioned anywhere in the docs.
https://aws.amazon.com/about-aws/whats-new/2020/12/aws-lambd... Is what you're talking about a new thing? Or respectfully, are you just wrong?
They probably have never requested service limit increase to unlock all of AWS.
Re: I put a real search engine into a Lambda, so you only pay when you search
#10Maybe a stupid question: why can't the indexer write directly to EFS, why does it write to s3 and lambda downloads it to EFS?
[deleted]