Honeycomb Maps Docs

Appearance

Scaling Honeycomb Maps ​

Overview ​

Honeycomb Maps provides two primary scaling options to optimize performance and handle varying workloads:

  1. Warehouse sizing - Adjust compute resources for query execution
  2. Application scaling - Increase service instances to handle high user concurrency

Warehouse Sizing ​

About the Honeycomb App Warehouse ​

All queries executed within Honeycomb Maps utilize a dedicated Snowflake warehouse named HONEYCOMB_APP_WAREHOUSE. This warehouse is automatically created during the application installation process and is used for:

  • Previewing SQL results in the editor
  • Loading data for map visualization
  • Executing queries when viewing shared maps

Default Configuration ​

The HONEYCOMB_APP_WAREHOUSE is created with an X-SMALL size by default. This configuration is suitable for most standard queries and typical usage patterns.

Adjusting Warehouse Size ​

For compute-intensive queries or large datasets that require more processing power, you can increase the warehouse size.

Prerequisites ​

  • HONEYCOMB_APP_ADMIN application role

Procedure ​

Execute the following stored procedure to change the warehouse size:

sql
CALL <HONEYCOMB_MAPS>.CONFIG.SET_WAREHOUSE_SIZE('MEDIUM');
CALL <HONEYCOMB_MAPS>.CONFIG.SET_WAREHOUSE_SIZE('MEDIUM');

Note: Replace <HONEYCOMB_MAPS> with your application name if you used a different name during installation.

Available Warehouse Sizes ​

  • X-SMALL (default)
  • SMALL
  • MEDIUM
  • LARGE
  • X-LARGE
  • 2X-LARGE
  • 3X-LARGE
  • 4X-LARGE

Important: Increasing warehouse size will increase compute costs. Monitor usage and adjust sizing based on your performance requirements and budget.

When to Increase Warehouse Size ​

Consider increasing the warehouse size when:

  • Queries are taking longer than expected to complete
  • Users are experiencing delays when loading maps with large datasets
  • Complex aggregations or joins are performed frequently
  • Preview operations in the SQL editor are slow

Application Scaling ​

About Application Scale ​

By default, Honeycomb Maps runs on a single SMALL compute pool node with one service instance. Due to Honeycomb Maps' efficient client-side compute architecture, this default configuration can support dozens of concurrent users.

Default Capacity ​

  • Compute pool: 1 SMALL node
  • Service instances: 1
  • Typical capacity: Dozens of concurrent map loads

Horizontal Scaling ​

For enterprises with high concurrency requirements, Honeycomb Maps can be scaled horizontally by adding more service instances and increasing compute pool capacity.

Prerequisites ​

  • HONEYCOMB_APP_ADMIN application role

Procedure ​

Execute the following stored procedure to scale the application:

sql
CALL <HONEYCOMB_MAPS>.CONFIG.SET_APPLICATION_SCALE(2);
CALL <HONEYCOMB_MAPS>.CONFIG.SET_APPLICATION_SCALE(2);

Note: Replace <HONEYCOMB_MAPS> with your application name if you used a different name during installation.

Scale Range ​

  • Minimum: 1 (default)
  • Maximum: 8

Cost Implications ​

Scaling the application increases the number of service instances and compute pool resources, which will increase costs. Plan your scaling strategy based on actual usage patterns and requirements.

Rolling Back Changes ​

To return to default settings:

sql
-- Reset warehouse to X-SMALL
CALL <HONEYCOMB_MAPS>.CONFIG.SET_WAREHOUSE_SIZE('X-SMALL');

-- Reset application scale to 1 instance
CALL <HONEYCOMB_MAPS>.CONFIG.SET_APPLICATION_SCALE(1);
-- Reset warehouse to X-SMALL
CALL <HONEYCOMB_MAPS>.CONFIG.SET_WAREHOUSE_SIZE('X-SMALL');

-- Reset application scale to 1 instance
CALL <HONEYCOMB_MAPS>.CONFIG.SET_APPLICATION_SCALE(1);

Copyright © 2025 Honeycomb Maps