Heikki Hellgren
Heikki Hellgren
The only problem is that it's slow when there are _a lot_ of entities (10000+). This shows in both search and in catalog so I would think it's because of...
> * for search, entities are authorized result-by-result (for technical reasons related to the underlining search engines) but there is a mechanism to put a "cap" in case a request...
Oh, so conditional permissions are not handled by the permission backend? If so, then yes, caching in the router won't help a lot. I will try adding a `search` table...
So I made the key value index (concurrently for postgres) and it seems it replaces the separate indexes for key and value completely. Those are not used anymore at all...
So applied the index to another instance. Here are the results: # Catalog search key+value index Query plan query used: ```sql SELECT * FROM final_entities LEFT JOIN search ON final_entities.entity_id...
@freben yeah those could be added there, a bit wrong issue maybe 😆
Not stale, needs a rebase
Hey, will check once back at the hotel