support the lambda.norpc tag on the go1.x runtime #456
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
This enhances the
-tags lambda.norpc
build option to work on thego1.x
runtime. Before it only worked onprovided
andprovided.al2
.This also:
invoke_loop.go
code to more directly implement the RuntimeAPI, rather than having to shim through thefunction.go
RPC layer. This makes it easier to build RuntimeAPI aware features without plumbing it through unused in the RPC version of the runtime. We might also consider in future making-tags lambda.norpc
the default build mode, if we can later identify no other required use of the RPC server.added some super simple benchmark script that can demonstrate a marginally improved throughput on the go1.x runtime
data:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.