# Meaning of configuration options ( General purpose or Optimized for Vectors) for azure erverless

**URL:** <https://discuss.elastic.co/t/meaning-of-configuration-options-general-purpose-or-optimized-for-vectors-for-azure-erverless/383654>\
**Category:** Elastic Search\
**Tags:** serverless\
**Created:** [November 25, 2025, 3:09pm UTC](https://discuss.elastic.co/t/meaning-of-configuration-options-general-purpose-or-optimized-for-vectors-for-azure-erverless/383654 "2025-11-25T15:09:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![RobinSteil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robinsteil/32/145823_2.png) [@RobinSteil](https://discuss.elastic.co/u/RobinSteil)\
**Post date:** [November 25, 2025, 3:09pm UTC](https://discuss.elastic.co/t/meaning-of-configuration-options-general-purpose-or-optimized-for-vectors-for-azure-erverless/383654/1 "2025-11-25T15:09:09Z")

</div>

What do the configuration options ( General purpose or Optimized for Vectors) for azure erverless mean.

[I found this blog but it does not contain any specifics.](https://www.elastic.co/blog/elastic-cloud-serverless-google-cloud-general-availability)

The Azure docs have nothing aswell (it told me I cant link to it here)

I could not find any docs about the difference between General purpose or Optimized for Vectors and what I should use when doing hybrid retrival RAG.

Could someone provide guidance on this choice?

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [November 27, 2025, 5:49am UTC](https://discuss.elastic.co/t/meaning-of-configuration-options-general-purpose-or-optimized-for-vectors-for-azure-erverless/383654/2 "2025-11-27T05:49:14Z")

</div>

We no longer provide the _Optimized for Vectors_ option in the UI, it should only be visible in the API.

The short answer is, unless you have very specific needs then you want _General Purpose_.

For most search use cases, including text search, as well as most vector and hybrid search use cases, _General Purpose_ is the best fit.

_Vector Optimized_ is weighted to provide more RAM relative to CPU and Disk for use cases that rely on dense vectors with HNSW (which is a memory intensive algorithm).  
By default, Serverless uses [DiskBBQ](https://www.elastic.co/search-labs/blog/diskbbq-elasticsearch-introduction) instead of HNSW which does not that same dependency on RAM.