search

unum-cloud / ucall

Web Serving and Remote Procedure Calls at 50x lower latency and 70x higher bandwidth than FastAPI, implementing JSON-RPC & REST over io_uring ☎️
https://unum-cloud.github.io/ucall/
Apache License 2.0
1.13k stars 42 forks source link

Feature: Auto-selecting the right native implementation #66

Open ashvardanian opened 1 year ago

ashvardanian commented 1 year ago

Describe what you are looking for

It's quite easy and cheap to pick the right underlying engine on startup. Much more reasonable for the user to replace rich_posix with rich_uring and understand the difference between POSIX and io_uring backends. I suggest:

  1. Deprecating the rich vs. native distinction.
  2. Auto-selecting between POSIX and io_uring.

It poses a question. If a function is only using built-in Python types, can we avoid the costly 2-layer decorator, and just pass it to the native implementation?

Can you contribute to the implementation?

Is your feature request specific to a certain interface?

Official Python bindings

Contact Details

No response

Is there an existing issue for this?

Code of Conduct

ashvardanian commented 1 year ago

@ishkhan42, is this already merged?