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
What would you like to be added/modified:
At present, Sedna's joint inference tasks require users to write business logic based on the SDK provided by Sedna (that is, users' businesses need to be coupled with Sedna's joint inference framework). For users, this incurs a high cost of use. Firstly, users need to be familiar with Sedna's SDK, and secondly, they also need to be familiar with container technology. Undoubtedly, this will deter most users.
Based on the above pain points, we propose to strip the SDK from the inference paradigm. Users only need to perform simple model configurations and can achieve the rapid deployment of inference tasks without programming based on Sedna's SDK. Why is this needed:
Reduce the usage cost for users.
The text was updated successfully, but these errors were encountered:
What would you like to be added/modified:
At present, Sedna's joint inference tasks require users to write business logic based on the SDK provided by Sedna (that is, users' businesses need to be coupled with Sedna's joint inference framework). For users, this incurs a high cost of use. Firstly, users need to be familiar with Sedna's SDK, and secondly, they also need to be familiar with container technology. Undoubtedly, this will deter most users.
Based on the above pain points, we propose to strip the SDK from the inference paradigm. Users only need to perform simple model configurations and can achieve the rapid deployment of inference tasks without programming based on Sedna's SDK.
Why is this needed:
Reduce the usage cost for users.
The text was updated successfully, but these errors were encountered: