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
@Enkosz More like I wanted it to persist even after killing the app. So that I don't have to generate superClusterIndex again. The data I am handling is big like close to 70000 records. I was checking if I can save it in some storage so that each time user opens the app after killing, the indices generated are available.
I'm wondering the same. My use case: running on servers behind a load balancer, with multiple sessions each clustering their own set of data. Each session is for a group of users that want to see the same clusters but may be hitting different servers. So I'm wondering if it's feasible to serialize the index and persist to a DB.
Activity
sgiannino commentedon Mar 28, 2023
What do you mean by caching? You could simply save it into a singleton variable or whatever and use it as you need it.
melbinexperion commentedon Mar 29, 2023
@Enkosz More like I wanted it to persist even after killing the app. So that I don't have to generate superClusterIndex again. The data I am handling is big like close to 70000 records. I was checking if I can save it in some storage so that each time user opens the app after killing, the indices generated are available.
meta-meta commentedon Nov 3, 2023
I'm wondering the same. My use case: running on servers behind a load balancer, with multiple sessions each clustering their own set of data. Each session is for a group of users that want to see the same clusters but may be hitting different servers. So I'm wondering if it's feasible to serialize the index and persist to a DB.
LeoMiguelB commentedon May 22, 2024
@meta-meta @melbinexperion #134 explains how to serialize index