1.9.2 - Indexing and Search Performance ContentBrowser
In general I really like Dash and the features it provides. One of the most important feature for me is the ContentBowser because I have many assets and many projects. For quick prototyping and world building I wanted to rely on the ContentBrowser to get all assets I need from my other projects and one library project I set up, that contains only assets. Sadly (even with AI feature disabled) computing new assets and searching for assets is too slow (depending on asset types i t can take seveeal minutes fornonly ~100) items. I'm wondering which information is stored and computed for each asset to take such a long time? I have around 50k-55k assets - if I open my library project (which contains 47.000) and then open Dash it needs ~15 minutes to even initialize all the already indexed items. Searching in this project via Dash also takes ~1 minute. Like that it's really unusble for me 
As a PoC I set up a simply RocksDB where I added all my assets with basic information like name, UserAssetData, Path and Type. Indexing all items (60k, because I include types that Dash doesn't include) with these information takes less then 30 seconds. Searching for e. g. a name takes less then 1second. That's why I'm wondering what kind of backend dash is using to index the data and look up items and if there is anything planned to optimize/change that?
As a PoC I set up a simply RocksDB where I added all my assets with basic information like name, UserAssetData, Path and Type. Indexing all items (60k, because I include types that Dash doesn't include) with these information takes less then 30 seconds. Searching for e. g. a name takes less then 1second. That's why I'm wondering what kind of backend dash is using to index the data and look up items and if there is anything planned to optimize/change that?