Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Caching SeachEngine Results

Thanks Mickael, i will investigate a bit on possiblity of maintaining my own cache. But i fear i might need pay a high price from complexity point of view. May be its better if this can be a slow running computer which can be taken in separate async computer setup.

Thanks for your valuable advice :)

On Sun, Jun 30, 2019, 23:09 Mickael Istria <mistria@xxxxxxxxxx> wrote:

No, I don't think there is caching at this level, but there is some caching a bit deeper on the stack (so the request would complete a bit faster, but the search would still happen). Caching wouldn't make much sense by default because search result can be big objects, the same search is rarely run multiple times in a row without other change in the code, in general any code change may alter search result, so it would basically cost a lot of memory for objects that are unlikely safe to reuse, so it's not something that makes sense to implement by default. But in your context where you are controlling the request and can guess what may invalidate it or not and know whether it's likely to be reused or not, implementing a cache can be profitable.

eclipse-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top