ClickHouse® is a column-oriented database management system (DBMS) for online analytical processing of queries (OLAP). Especially this software stack is exercising Intel In-Memory Analytics Accelerator (IAA) through hardware-assisted codec.
The workload contains dockers image of clickhouse-iaa-base which include a fresh clickhouse server. The Clickhouse server can be set up using either Kubernetes or Docker as a backend. Starting clickhouse server on IAA-enabled Host using Docker is as follows (if the IAA is not well set up in the host, it falls back to software codec)
docker run --rm --detach --privileged --network host intel/intel-optimized-clickhouse
The BIOS must be configured with VT-d and PCI ENQCMD enabled, as follows:
EDKII Menu → Socket Configuration → IIO Configuration → Intel VT for directed IO (VT-d) → Intel VT for directed IO → Enable EDKII Menu → Socket Configuration → IIO Configuration → PCI ENQCMD/ENQCMDS → Yes
The VT-d must be enabled from the kernel command line, which can be checked with the output of intel_iommu from "cat /proc/cmdline":
sudo grubby --update-kernel=DEFAULT --args="intel_iommu=on,sm_on iommu=pt" sudo reboot
The IAA devices need to be enabled as well. The enabling commands can be done by the host or can be integrated to the docker image. "-v /dev:/dev" is needed as docker run option if the docker is supposed to enable the host IAA device. Below are the commands to enable 4 IAA devices:
accel-config load-config -c ./accel-iaa-4d1g8e.conf accel-config enable-device iax1 accel-config enable-wq iax1/wq1.0 accel-config enable-device iax3 accel-config enable-wq iax3/wq3.0 accel-config enable-device iax5 accel-config enable-wq iax5/wq5.0 accel-config enable-device iax7 accel-config enable-wq iax7/wq7.0
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
无需登录使用专属域名
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
Harbor Proxy Repository 对接专属域名
Portainer Registries 加速拉取
Nexus3 Docker Proxy 内网缓存
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
manifest unknown
no matching manifest(架构)
invalid tar header(解压)
TLS 证书失败
DNS 超时
410 Gone 排查
402 与流量用尽
401 认证失败
429 限流
D-Bus 凭证提示
413 与超大单层
来自真实用户的反馈,见证轩辕镜像的优质服务