Skip to content
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.

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

Caching #5

Open
abhinavtripathy opened this issue Dec 11, 2019 · 3 comments
Open

Caching #5

abhinavtripathy opened this issue Dec 11, 2019 · 3 comments
Assignees
Labels
enhancement New feature or request question Further information is requested

Comments

@abhinavtripathy
Copy link
Member

abhinavtripathy commented Dec 11, 2019

Currently the API takes 2-3 seconds to respond which a long amount of time. The idea is make this process faster through caching while being true to the problem and understanding the context with images.

@abhinavtripathy abhinavtripathy added the enhancement New feature or request label Dec 11, 2019
@abhinavtripathy abhinavtripathy self-assigned this Dec 11, 2019
@abhinavtripathy
Copy link
Member Author

@rishab2113 For caching and detecting similar images we can take some details from here

@abhinavtripathy
Copy link
Member Author

abhinavtripathy commented Dec 18, 2019

A proposed solution would be to compare a similarity between the two raw Base64 strings and if it is above a certain threshold, one could just written the string cached in the database like redis. A good implementation of this would be with Redis and NodeJS.

@abhinavtripathy abhinavtripathy added the question Further information is requested label Dec 18, 2019
@abhinavtripathy abhinavtripathy changed the title Caching for Faster Speed in Deployment Caching Dec 18, 2019
@abhinavtripathy
Copy link
Member Author

As an alternative to Redis, Memcached can be used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant