Adds recommendation about choosing project profile

[szabosteve]

Overview

This PR adds guidance for selecting the appropriate project profile based on the use case. It outlines when to use the General Purpose (GP) profile versus the Vector Optimized (VO) profile.

[github-actions]

🔍 Preview links for changed docs

• solutions/search/vector/bring-own-vectors.md
• solutions/search/vector/dense-vector.md
• solutions/search/vector/knn.md

[shubhaat]

Suggesting additional changes to the Billing dimensions page: https://github.com/elastic/docs-content/blob/ffcbcf3bb6b57e11caf9aa5ad0442c6418561dc9/deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md

I would suggest under the "Managing Elasticsearch Serverless costs" we add a section on "Profile selection" and add a blurb like

General Purpose profile v.s. Vector Optimized Profile

The General Purpose profile offers a great performance for the price especially for most search use cases. It is the right profile for full-text search, semantic search using ELSER or sparse vector embeddings, sparse vectors and dense vectors using compression such as BBQ (default on serverless). We recommend using the General Purpose instance for most search use cases.

We recommend using the Vector Optimized profile only for uncompressed dense vectors when you want better performance. Though the per VCU cost is the same for General Purpose and Vector Optimized profile, the Vector Optimized profile provides a larger amount of RAM for searchable data, so it leads to higher VCU consumption, and is more expensive while providing significantly better performance for uncompressed vector data.

[lcawl]

Suggesting additional changes to the Billing dimensions page: https://github.com/elastic/docs-content/blob/ffcbcf3bb6b57e11caf9aa5ad0442c6418561dc9/deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md

I had related updates already underway in #2744 so I've added this suggestion there.

[szabosteve]

@shubhaat I addressed your feedback in my latest commits. Lisa's PR (linked above) contains the changes you suggested for the billing dimensions page.

[shubhaat]

I think this is ok for now, but I think there will be big changes coming to the VO optimized profile based on feedback from Shay. We want to de-emphasize Vector optimized a LOT, and I wonder if we can make it clearer in the documentation that use VO only for very specific needs - when you need high memory for ingest/search. + @giladgal and @petegaleotti - I might want to rethink the docs updates once we know what we are doing in onboarding.

[shubhaat]

@szabosteve , @lcawl I suggest we stash this documentation update. @petegaleotti is working on a major change to the VO profile and competely removing this from the UI and deemphasizing it in the docs etc. Sorry for the thrash, and fast turnaround time.

[lcawl]

@szabosteve , @lcawl I suggest we stash this documentation update. @petegaleotti is working on a major change to the VO profile and competely removing this from the UI and deemphasizing it in the docs etc. Sorry for the thrash, and fast turnaround time.

Based on a chat with @petegaleotti today it seems like it's worth implementing the updates in serverless-elasticsearch-get-started.md for now and then revamping them again if the UI changes. IMO the changes in the vector.md file can be deferred for now.

[lcawl]

FYI I've reverted the changes to the getting started page in this PR and will make them in #2839 instead.

[petegaleotti]

General and vector optimized projects [vector-profiles]

I recommend changing that to "General purpose and vector...".