Who is this for?

This is an introductory topic for developers deploying and optimizing ClickHouse on Arm-based Linux environments using Google Cloud C4A virtual machines powered by Axion processors, to evaluate ClickHouse performance and behavior on Arm-based infrastructure.

What will you learn?

After completing this Learning Path, you'll be able to perform the following tasks:

  • Provision an Arm-based SUSE SLES virtual machine on Google Cloud using C4A (Axion processors)
  • Configure Google Cloud Pub/Sub for real-time log ingestion
  • Deploy and validate ClickHouse on a SUSE Linux Arm64 (Axion) VM
  • Build a streaming ETL pipeline using Apache Beam and Google Dataflow
  • Ingest real-time Pub/Sub data into ClickHouse using Dataflow
  • Validate end-to-end data flow from Pub/Sub to ClickHouse
  • Perform baseline and analytical query benchmarking on ClickHouse running on Arm64
  • Measure and report query latency (including p95) on Axion processors

Prerequisites

Before starting, you'll need the following prerequisites:

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll deploy ClickHouse on an Arm-based Google Cloud C4A virtual machine and assemble a streaming analytics pipeline. After exploring C4A (Neoverse-V2) instances, you’ll provision a c4a-standard-4 SUSE Linux VM, create a firewall rule to open TCP port 8123, and install ClickHouse alongside the Google Cloud CLI. Then, you’ll set up Pub/Sub and required IAM so Apache Beam on Dataflow can stream events into ClickHouse. By the end, you’ll validate end-to-end ingestion from Pub/Sub to ClickHouse and run baseline and analytical queries, capturing latency metrics (including p95) to evaluate ClickHouse behavior on Axion processors.
Next