Configure custom t-shirt sizes for Lumi Enterprise

Early access

Virtual tier is an early access feature. If you don't have access to the virtual tier, contact your Imply support representative.

By default, Imply Lumi provides a set of predefined t-shirt sizes for virtual compute pools. If need different sizing than the defaults, you can define custom t-shirt sizes in Terraform. When you create a custom t-shirt size, you have the option to specify the instance type, node count, and query concurrency that best match your workload requirements and performance needs.

Custom t-shirt sizes are only supported for Lumi Enterprise deployments on AWS.

Prerequisites

To configure custom t-shirt sizes, you need a Lumi user with the Admin role. For information on roles and permissions, see Manage roles.

Predefined t-shirt sizes

The following table shows the predefined t-shirt sizes available in Lumi Enterprise:

Size	Name	Instance type1	Max concurrency	Node count
xs	X-small	i4i.xlarge	4	2
s	Small	i4i.xlarge	4	4
m	Medium	i4i.xlarge	4	8
l	Large	i4i.2xlarge	8	8
xl	X-large	i4i.4xlarge	12	8
2xl	2X-large	i4i.4xlarge	12	16
3xl	3X-large	i4i.4xlarge	12	32

¹ Instance types are AWS EC2 instance types.

Custom t-shirt sizes

If the predefined sizes don't meet your requirements, you can create custom t-shirt sizes in Terraform. Custom t-shirt sizes replace the predefined sizes entirely; they are not appended to the existing list.

Create a custom size

To create a custom t-shirt size, set the virtual_compute_tshirt_sizes property in main.tf:

variable "virtual_compute_tshirt_sizes" {
  type = list(object({
    size            = string
    instance_type   = string
    node_count      = number
    name            = optional(string)
    max_concurrency = optional(number)
  }))

The following constraints apply:

• size must be a unique string value
• node_count and max_concurrency must be integers greater than or equal to 1
• max_concurrency defaults to 4 if not specified
• instance_type must be one of the following supported instance types:
  • i3en.xlarge through i3en.6xlarge
  • i4i.xlarge through i4i.8xlarge
  • is4gen.xlarge through is4gen.8xlarge

The following example shows three custom t-shirt sizes:

  virtual_compute_tshirt_sizes = [
    {
      size            = "sc"
      name            = "small_custom"
      instance_type   = "i4i.xlarge"
      node_count      = 2
      max_concurrency = 4
    },
    {
      size          = "mc"
      name          = "medium_custom"
      instance_type = "i4i.xlarge"
      node_count    = 4
      max_concurrency = 4
    },
    {
      size          = "lc"
      name          = "large_custom"
      instance_type = "i4i.xlarge"
      node_count    = 8
      max_concurrency = 4
    },
  ]
}

After configuring a custom t-shirt size in Terraform, run terraform apply to apply the changes. The changes propagate to the Lumi UI automatically. New sizes appear grayed out in the Lumi UI while Lumi provisions the necessary resources.

Modify or remove a custom size

To modify or remove a custom t-shirt size, update the virtual_compute_tshirt_sizes property in main.tf, then run terraform apply.

Keep the following in mind when modifying or removing a custom t-shirt size that is currently assigned to a virtual compute pool:

• Removing a size that is in use causes the pool to stop serving queries and terminates all in-flight queries.
• Modifying a size may affect the pool's ability to serve queries. For example, changing the instance type may cause the pool to stop serving queries.

To restore service, select an available size for the pool in Data management > Virtual compute pools.

Learn more

For more information, see the following topics:

• Data tiers overview for details on the virtual tier.
• Configure tiering rules to add and manage tiering rules.
• Configure deletion rules to set up automatic data deletion.