<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CHR on XGA</title><link>https://www.xga.ie/tags/chr/</link><description>Recent content in CHR on XGA</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Thu, 04 May 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://www.xga.ie/tags/chr/index.xml" rel="self" type="application/rss+xml"/><item><title>High BGP CPU usage on Mikrotik CHR</title><link>https://www.xga.ie/posts/mikrotik-bgp-high-cpu/</link><pubDate>Thu, 04 May 2023 00:00:00 +0000</pubDate><guid>https://www.xga.ie/posts/mikrotik-bgp-high-cpu/</guid><description>&lt;p&gt;While experimenting with BGP using Mikrotik Cloud Hosted Routers (CHR) on low-power, shared X86 hardware, it became apparent that CPU usage was an issue with full feeds.&lt;/p&gt;
&lt;h2 id="before"&gt;
 Before
 &lt;a class="heading-link" href="#before"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;The router was handling approximately 420-thousand IPv6 routes on a single CPU.
When I tried to view the routes in WinBox or SSH, the CPU would go to 100% and remain there, leaving the router unresponsive until rebooted.&lt;/p&gt;</description></item></channel></rss>