We measured on-premise resource usage for the Neblex Worker, our local integration runtime, across 15 everyday flows and three large workloads. Idle, it used about 25 MB of memory. Fourteen of the 15 flows averaged 29 to 94 MB, and a 1 million row load into a cloud database peaked at about 450 MB. CPU stayed low except during heavy matching.

The question IT and security teams ask first

A request we hear often from prospects is to move data from a database inside their network to a cloud warehouse, on a schedule, without opening that database to the internet. That means installing software inside the network: an agent or a runtime. Before anyone discusses the warehouse, IT and security teams ask what that software will cost their servers and what it can reach.

The usual answer is a page of minimum requirements. We wanted to answer with measured numbers, so we ran the Neblex Worker through a week of tests, from small event flows to million-row loads, and recorded what it used.…