<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Benchmarking on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/benchmarking/</link><description>Recent content in Benchmarking on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Sun, 08 Feb 2026 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/benchmarking/atom.xml" rel="self" type="application/rss+xml"/><item><title>Multi-Node, Multi-Disk MinIO Cluster Performance Testing Under Different Erasure Code Configurations</title><link>https://www.chenshaowen.com/en/blog/multi-node-multi-disk-minio-cluster-performance-test-in-different-erasure-code-configurations.html</link><pubDate>Sun, 08 Feb 2026 00:00:00 +0000</pubDate><atom:modified>Sun, 08 Feb 2026 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/multi-node-multi-disk-minio-cluster-performance-test-in-different-erasure-code-configurations.html</guid><description>1. Erasure Code Configuration The default erasure parity configuration is as follows:
Erasure Set Size Default Parity (EC:M) 1 EC:0 2-3 EC:1 4-5 EC:2 6 - 7 EC:3 8 - 16 EC:4 The maximum parity is ERASURE_SET_SIZE/2, meaning the number of parity blocks cannot exceed the number of data blocks.</description><dc:creator>微信公众号</dc:creator><category>MinIO</category><category>Storage</category><category>Operations</category><category>Performance</category><category>Testing</category><category>Benchmarking</category><category>Performance Testing</category></item><item><title>Multi-Node, Multi-Disk MinIO Cluster Performance Testing Under Different Erasure Code Configurations on IPoIB</title><link>https://www.chenshaowen.com/en/blog/multi-node-multi-disk-minio-cluster-performance-test-in-different-erasure-code-configurations-on-ipoib.html</link><pubDate>Sun, 08 Feb 2026 00:00:00 +0000</pubDate><atom:modified>Sun, 08 Feb 2026 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/multi-node-multi-disk-minio-cluster-performance-test-in-different-erasure-code-configurations-on-ipoib.html</guid><description>The earlier tests found the bottleneck in the NIC; this post adds supplementary testing under IPoIB.
1. MinIO Cluster Environment 1.1 Creating the MinIO Cluster 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 export CONTAINER_CLI=nerdctl export IMAGE=minio/minio:RELEASE.</description><dc:creator>微信公众号</dc:creator><category>MinIO</category><category>Storage</category><category>Distributed Systems</category><category>Erasure Coding</category><category>IPoIB</category><category>Performance Testing</category><category>Benchmarking</category></item><item><title>Using HAProxy to Proxy MinIO and Performance Testing</title><link>https://www.chenshaowen.com/en/blog/using-haproxy-to-proxy-minio-and-performance-testing.html</link><pubDate>Sun, 08 Feb 2026 00:00:00 +0000</pubDate><atom:modified>Sun, 08 Feb 2026 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/using-haproxy-to-proxy-minio-and-performance-testing.html</guid><description>1. Preparing the Configuration Files MinIO cluster 1 mc admin info local 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 ● minio1:9000 Uptime: 55 minutes Version: 2025-04-22T22:12:26Z Network: 2/2 OK Drives: 4/4 OK Pool: 1 ● minio2:9000 Uptime: 55 minutes Version: 2025-04-22T22:12:26Z Network: 2/2 OK Drives: 4/4 OK Pool: 1 ┌──────┬───────────────────────┬─────────────────────┬──────────────┐ │ Pool │ Drives Usage │ Erasure stripe size │ Erasure sets │ │ 1st │ 0.</description><dc:creator>微信公众号</dc:creator><category>MinIO</category><category>HAProxy</category><category>Storage</category><category>Proxy</category><category>Performance Testing</category><category>Benchmarking</category></item><item><title>Using VLLM Benchmark for Model Performance Testing</title><link>https://www.chenshaowen.com/en/blog/using-vllm-benchmark-to-test-model-performance.html</link><pubDate>Tue, 05 Aug 2025 00:00:00 +0000</pubDate><atom:modified>Tue, 05 Aug 2025 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/using-vllm-benchmark-to-test-model-performance.html</guid><description>VLLM Benchmark is a tool provided by VLLM for testing model performance, supporting a variety of inference backends. This article mainly records some of the process of using VLLM Benchmark to test model performance.
1. Starting the Model Service 1 2 3 4 5 6 7 8 9 10 11 12 13 14 python -m vllm.</description><dc:creator>微信公众号</dc:creator><category>AI</category><category>VLLM</category><category>Benchmarking</category><category>Model Performance</category><category>Testing</category></item></channel></rss>