spinframework / spinframework/spin
Performance is slow on HTTP Trigger
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
Issue
I appear to have quite some overhead caused by Spin. I compiled an application as a WASM package and benchmark the HTTP speed against a native class instance and get the below performance for my calls:
Is there any good practice on speeding this up? Can the HTTP connection be re-used?
Python
Typescript
General
- Spin version (
spin --version): spin 2.2.0 (eebfae1 2024-01-30) - Installed plugin versions (
spin plugins list --installed)
cloud 0.7.0 [installed]
js2wasm 0.6.1 [installed]
py2wasm 0.3.2 [installed]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported HTTP Trigger benchmark with Spin 2.2.0, comparing the WASM application with the native class instance for the Python and TypeScript cases. Check the installed cloud, js2wasm, and py2wasm plugin versions, then determine whether HTTP connections can be reused and document the cause of the overhead or the applicable optimization guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust, typescript, wasm
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100