We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hoxy is phenomenal, but isn't the most performant - at higher workloads, hoxy seems to be the component that is causing the greatest strain in James.
hoxy
We should implement a small little wasm proxy that will provide the functionality of hoxy that we use, while being minimal and fast.
Since we'll control the proxy, this will also make issues like #399 directly solvable
The text was updated successfully, but these errors were encountered:
No branches or pull requests
hoxy
is phenomenal, but isn't the most performant - at higher workloads,hoxy
seems to be the component that is causing the greatest strain in James.We should implement a small little wasm proxy that will provide the functionality of
hoxy
that we use, while being minimal and fast.Since we'll control the proxy, this will also make issues like #399 directly solvable
The text was updated successfully, but these errors were encountered: