|     Documentation    |     Premium Support

InMemoryFeatureSource vs SqliteFeatureSource(in-memory connection)

My question is which one has better performance?

Using your native InMemoryFeatureSource or SqliteFeatureSource and use the in-memory connection string?
when I talk about performance, I mean memory consumption and tile loading (query on features)

I believe as long as SQLite is a very stable package and too many developers try to improve the performance, maybe SQLite will be the better option.

Hi Mahdi,

I agree with you, I would recommend SqlLiteFeatureSource.

If you cache the features in InMemoryFeatureSource, it’s fast, but it might not be worth, because it would occupy lots of memory, and if there’re too many features in InMemoryFeatureSource, build index is required, otherwise, it’s very slow.