New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Better Async methods to handle frame results streams #4

Open

Anindyadeep opened this issue Mar 4, 2023 · 0 comments

Member

Anindyadeep commented Mar 4, 2023

In the current version of the API, we have implemented a very simple and a naïve way to handle those requests. We have:

Implemented a queue (acting like a message queue) to store all those requests
Batch every 5-6 concurrent requests and then treat as one request to put into fastdtw algorithm.
And then return the response to the frontend.

But we need some better techniques to do that more effectively and in an optimized manner. Some ways to get started with are:

Getting started with Apache FLink to handle those requests.
Implementing Async message queues
etc

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment