Skip to main content

14 docs tagged with "BEP"

View All Tags

Add no-code Rate Limiter step

The no-code Rate Limiter bot step enables you to control the number of records passing through the step within a specific time frame. This is particularly beneficial for implementing rate-limiting at a granular level, such as per AI Agent, reducing the impact on resources when two AI Agents are running in a single environment.

Apply BEP Worker

A Worker is a single instance of a Worker application process started by BEP to process BEP Worker tasks.

Calculate capacity

To plan capacity means to ensure the availability of a cost-effective capacity that meets or exceeds the business needs as established in Service Level Agreements (SLAs) at any given time. Within the context, capacity is defined as the maximum load the Work.AI platform can handle.

Estimate resources for AutoML execution

This article provides recommendations on how to adjust AutoML Worker parameters, such as CPU and memory consumption, for better cluster utilization and throughput.

Execute tasks with BEP Worker

The Worker scaling strategy is a mechanism for calculating an optimal Worker quantity to satisfy, to the maximum possible extent, the multiple task execution requirements on a cluster with fixed limited resources (non-elastic cluster). The strategy is supposed to adapt when cluster resources are added or removed.

Explore BEP components

Bot Execution Platform (BEP) is a platform allowing you to execute large volumes of tasks on a cluster in a scalable and fault-tolerant manner.

Java Native Worker

The Java native mechanism enables you to write and deploy custom pure Java-based Workers with any libraries without additional loading or linking.

Manage BEP Worker execution

The Worker management system (WMS) starts and stops BEP Workers, as well as scales them up or down based on received streams of BEP Worker tasks queued from client apps.

Perform cluster autoscaling

To support cases with a non-constant load of available cluster resources and allow reducing TCO, you require elastic cluster scaling. Virtual machines (VM) in the cluster are added on demand and reduced when there is no load and they are no longer needed.