Logo-amall

Is anyone using meilisearch for user specific data sets? We have basically a CRM, and so each user has a different set of data to search/filter through (all their contacts). Weve used meili for site wide stuff but havent messed with user specific data sets and Im wondering if its up to the task at it's current stage. If there's any performance hits it takes or lag when updating user specific indexes? Id imagine each user would have a data set of anywhere between 10 and 50,000 entries.

Last active 5 months ago

2 replies

20 views

  • TI

    Is anyone using meilisearch for user specific data sets? We have basically a CRM, and so each user has a different set of data to search/filter through (all their contacts).

    Weve used meili for site wide stuff but havent messed with user specific data sets and Im wondering if its up to the task at it's current stage. If there's any performance hits it takes or lag when updating user specific indexes?

    Id imagine each user would have a data set of anywhere between 10 and 50,000 entries.

  • GU

    Hi @Tim White

    Although Meilisearch does not have a limit on the number of indexes, it is possible that the file system limits it and forces you to increase the number of files that can be opened at the OS level. (depends on the operating system)

    Instead, I would advise you to store all your users' documents in a single index and take advantage of the feature; this is a JWT that can be used to ensure that the consumer (an end user), can only see his documents when making a search request.

    Concentrating the documents in a single index also takes advantage of the feature that aims to speed up the indexing speed. Batch operations are built from document update jobs targeting the same index.

    The potential drawback is that you will be forced to have the same filterable/sortable and searchable fields for each of your users because the parameters are at the index level. (However, you can use a custom UI on the front end based on the end user, e.g., this one has X facets and that one has Y facets, if that is necessary for your product)

    If your end users' documents share the same schema and they all need to use the same search UI/UX, this doesn't seem to be a direct problem.

Last active 5 months ago

2 replies

20 views