Application Launcher

Your SearchStax subscription level is sized to handle both your typical load and peak demand with enough headroom for stability. Acquia evaluates a rolling window of your usage based on several factors:

Factor	What Acquia considers
Query volume and concurrency	Average queries per minute or hour and the highest spikes (peak QPS).
Index size and number of collections or cores	Larger datasets and more collections require more resources.
Redundancy and availability	Replica counts, high-availability requirements, and your SLA tier.
Traffic patterns	Seasonality, marketing events, and the share of traffic generated by bots versus real users.

Verifying whether your current plan is correctly sized

Follow these steps to assess whether your subscription still matches your actual usage:

Review your metrics.
Navigate to your SearchStax metrics dashboard or your application logs and examine at least the last 30-90 days of data. Note peak hours, maximum QPS, and any sustained periods where resource warnings or throttling occurred.
Compare sustained peaks to your plan limits.
If you frequently run near capacity or see throttling, you may need to upgrade. If your usage has significantly declined for multiple months, a downgrade may be possible.
Identify non-human traffic.
If bots contribute a high share of queries, you may be able to remain on your current plan by implementing bot mitigation and application-level throttling. For more information, visit Block excessive crawling of Drupal Views or search results.
Share your findings with Acquia Support.
Contact Acquia Support. The support team confirms the sizing assumptions used for your subscription and advises on whether your plan is right-sized. The Support team also helps you evaluate whether optimization or a plan change is the best path forward.

Note

If you are unsure whether your traffic spikes are caused by real users or bots, prioritize reviewing your web server access logs for user-agent strings before you make a plan change. It is more cost-effective to address bot traffic than to upgrade your subscription.

Factor	What Acquia considers
Query volume and concurrency	Average queries per minute or hour and the highest spikes (peak QPS).
Index size and number of collections or cores	Larger datasets and more collections require more resources.
Redundancy and availability	Replica counts, high-availability requirements, and your SLA tier.
Traffic patterns	Seasonality, marketing events, and the share of traffic generated by bots versus real users.

Verifying whether your current plan is correctly sized

Follow these steps to assess whether your subscription still matches your actual usage:

Review your metrics.
Navigate to your SearchStax metrics dashboard or your application logs and examine at least the last 30-90 days of data. Note peak hours, maximum QPS, and any sustained periods where resource warnings or throttling occurred.
Compare sustained peaks to your plan limits.
If you frequently run near capacity or see throttling, you may need to upgrade. If your usage has significantly declined for multiple months, a downgrade may be possible.

Factor	What Acquia considers
Query volume and concurrency	Average queries per minute or hour and the highest spikes (peak QPS).
Index size and number of collections or cores	Larger datasets and more collections require more resources.
Redundancy and availability	Replica counts, high-availability requirements, and your SLA tier.
Traffic patterns	Seasonality, marketing events, and the share of traffic generated by bots versus real users.

Verifying whether your current plan is correctly sized

Follow these steps to assess whether your subscription still matches your actual usage:

Review your metrics.
Navigate to your SearchStax metrics dashboard or your application logs and examine at least the last 30-90 days of data. Note peak hours, maximum QPS, and any sustained periods where resource warnings or throttling occurred.
Compare sustained peaks to your plan limits.
If you frequently run near capacity or see throttling, you may need to upgrade. If your usage has significantly declined for multiple months, a downgrade may be possible.
Identify non-human traffic.
If bots contribute a high share of queries, you may be able to remain on your current plan by implementing bot mitigation and application-level throttling. For more information, visit Block excessive crawling of Drupal Views or search results.
Share your findings with Acquia Support.
Contact Acquia Support. The support team confirms the sizing assumptions used for your subscription and advises on whether your plan is right-sized. The Support team also helps you evaluate whether optimization or a plan change is the best path forward.

Note

Verifying whether your current plan is correctly sized

Verifying whether your current plan is correctly sized

Verifying whether your current plan is correctly sized

Did not find what you were looking for?

Did not find what you were looking for?

Determining the correct SearchStax subscription level for your traffic

Verifying whether your current plan is correctly sized

Determining the correct SearchStax subscription level for your traffic

Verifying whether your current plan is correctly sized

Determining the correct SearchStax subscription level for your traffic

Verifying whether your current plan is correctly sized

Did not find what you were looking for?

Did not find what you were looking for?