Frontend Pods

Overview

The frontend is a critical component of the UserWise system, responsible for handling all API requests and serving the UserWise dashboard. When any HTTP request reaches the subdomain you've configured for UserWise access, the frontend pods will be responsible for processing it.

Most of the requests that these pods will receive are documented here: https://docs.userwise.io

Configuration

The frontend and worker pods have separate configurations, both within the Kubernetes context and in terms of how you can fine-tune UserWise's runtime to work best with your specific use cases. The ability to customize settings allows you to tailor the system's behavior to match your specific requirements and optimize performance.

As of writing, the frontend pod has the following configuration options: Cluster Configuration (Helm Chart Variables) | Cluster Frontend Pod

Pod Sizing

A crucial aspect of optimizing the frontend pods is ensuring they are appropriately sized. At a minimum, each pod should have at least one process with at least four threads.

The root process and its threads will share memory where possible (very roughly similar to the distinction between heap and stack memory). In our production environments, we have found that one process with ten threads per pod is sufficient for general workloads. Such a pod would typically consume one CPU and one gigabyte of RAM (as defined in Kubernetes configurations).