<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CI on CoreDNS: DNS and Service Discovery</title><link>https://coredns.website.cncfstack.com/tags/ci/</link><description>Recent content in CI on CoreDNS: DNS and Service Discovery</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>CoreDNS - All Rights Reserved</copyright><lastBuildDate>Tue, 08 Aug 2017 22:50:37 +0100</lastBuildDate><atom:link href="https://coredns.website.cncfstack.com/tags/ci/index.xml" rel="self" type="application/rss+xml"/><item><title>CoreDNS Performance Testing</title><link>https://coredns.website.cncfstack.com/2017/08/08/coredns-performance-testing/</link><pubDate>Tue, 08 Aug 2017 22:50:37 +0100</pubDate><guid>https://coredns.website.cncfstack.com/2017/08/08/coredns-performance-testing/</guid><description>As CoreDNS is an inception level project under the CNCF which means we have access to the physical cloud infrastructure of Packet, a bare metal(!) cloud provider. Physical machines imply performance and also because you get an entire machine you can use them for performance metrics.
For CoreDNS we have a few Benchmark tests (from the Go standard library) that haven&amp;rsquo;t seen much use. Typically you run these before your change and then after your and then use a tool like benchcmp to compare the results and impress your PR&amp;rsquo;s reviewers.</description></item></channel></rss>