You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, we are so proud to use remix to improve our user experience and code cleanliness. But as our QPS grows (above 500), we increasingly need to consider performance and price, and I'm exploring rewriting the loader using rust or other high-performance languages. (Our loader contains a large number of database operations and intensive calculations, and the performance of nodejs is far inferior to lower-level languages such as go or rust). If all complex calculations are removed from nodejs, we can increase the load capacity of the loader and use a more scalable runtime such as v8 worker to host SSR alone.
From what I know about remix, we can return Response objects in loaders, I think we can forward loaders written in rust at this layer. The key to the problem is the data conversion protocol, how we can make the request just like the structure returned by defer util, and how to handle the situation of deserializing to Promise when SSR. I thought this might be similar to re-implementing defer by another programming language.
I would like to ask whether the deferred data conversion protocols are maintained in a long term and are willing to be made public. And I am trying to give a benchmark based on this to compare the performance gains of replacing loaders with other language versions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, we are so proud to use remix to improve our user experience and code cleanliness. But as our QPS grows (above 500), we increasingly need to consider performance and price, and I'm exploring rewriting the loader using rust or other high-performance languages. (Our loader contains a large number of database operations and intensive calculations, and the performance of nodejs is far inferior to lower-level languages such as go or rust). If all complex calculations are removed from nodejs, we can increase the load capacity of the loader and use a more scalable runtime such as v8 worker to host SSR alone.
From what I know about remix, we can return Response objects in loaders, I think we can forward loaders written in rust at this layer. The key to the problem is the data conversion protocol, how we can make the request just like the structure returned by defer util, and how to handle the situation of deserializing to Promise when SSR. I thought this might be similar to re-implementing defer by another programming language.
I would like to ask whether the deferred data conversion protocols are maintained in a long term and are willing to be made public. And I am trying to give a benchmark based on this to compare the performance gains of replacing loaders with other language versions.
Thank you for your time.
Beta Was this translation helpful? Give feedback.
All reactions