3 ms·
The startup I'm working at is basically trying to do exactly that as a service, but a one-off thing for a regular Python application shouldn't be as hard to fig
by callahad 4y ago
The startup I'm working at is basically trying to do exactly that as a service, but a one-off thing for a regular Python application shouldn't be as hard to figure out as it is. Can you link to the Mastodon thread (darn lack of search!) and we can continue there?
- simonw 4y agoHere's the Mastodon conversation: https://fedi.simonwillison.net/@simon/109682777068881522 https://fedi.simonwillison.net/@simon/109682777068881522 (I'm so close to building my own search engine just against my own content there.)
- callahad 4y agoI have Covid and it's late in the UK, but tried poking at wasmtime-py for the first time and got this far: https://gist.github.com/callahad/81b33e4e4456e4b27a5934c1a36cf7ff https://gist.github.com/callahad/81b33e4e4456e4b27a5934c1a36... If anyone else is awake and wants to pick up the baton... - CPU limits are just using an arbitrary amount of wasmtime "fuel". Would be worth looking into epoch interrupts instead. - Memory limits aren't implemented. Seems like wasmtime-py doesn't expose bindings to anything with a wasmtime::ResourceLimiter trait. - All i/o is going through tempfiles instead of dealing with proper interfaces.