<story><title>Garnet – A new remote cache-store from Microsoft Research</title><url>https://github.com/microsoft/garnet</url></story><parent_chain><item><author>whimsicalism</author><text>surprised to see a garbage collected language project (C# for Garnet) beat redis&amp;#x2F;dragonfly</text></item><item><author>west0n</author><text>From the benchmark performance charts(&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;microsoft.github.io&amp;#x2F;garnet&amp;#x2F;docs&amp;#x2F;benchmarking&amp;#x2F;results-resp-bench&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;microsoft.github.io&amp;#x2F;garnet&amp;#x2F;docs&amp;#x2F;benchmarking&amp;#x2F;results...&lt;/a&gt;), the throughput of the GET command exceeds that of Dragonfly by more than tenfold. While 50% latency is slightly higher than Dragonfly, the 99th percentile is slightly lower than Dragonfly. Both the throughput and latency of Garnet and Dragonfly are far better than Redis, indicating that Redis may require a significant performance optimization.</text></item></parent_chain><comment><author>pjmlp</author><text>Not all garbage collected languages are made equal, some of them, like C# and .NET, do provide all the performace knobs that are needed for C++ like coding.&lt;p&gt;People only have to learn how to use them, instead of placing all garbage collected languages into the same basket.&lt;p&gt;In this specific case, MSIL and .NET were designed to support C++ as well, and languages like C# and F# do have ways to access those features, and even if some feature isn&amp;#x27;t exposed at the language grammar level, you can emit the same MSIL that C++&amp;#x2F;CLI would generate.</text></comment>
<story><title>Garnet – A new remote cache-store from Microsoft Research</title><url>https://github.com/microsoft/garnet</url></story><parent_chain><item><author>whimsicalism</author><text>surprised to see a garbage collected language project (C# for Garnet) beat redis&amp;#x2F;dragonfly</text></item><item><author>west0n</author><text>From the benchmark performance charts(&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;microsoft.github.io&amp;#x2F;garnet&amp;#x2F;docs&amp;#x2F;benchmarking&amp;#x2F;results-resp-bench&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;microsoft.github.io&amp;#x2F;garnet&amp;#x2F;docs&amp;#x2F;benchmarking&amp;#x2F;results...&lt;/a&gt;), the throughput of the GET command exceeds that of Dragonfly by more than tenfold. While 50% latency is slightly higher than Dragonfly, the 99th percentile is slightly lower than Dragonfly. Both the throughput and latency of Garnet and Dragonfly are far better than Redis, indicating that Redis may require a significant performance optimization.</text></item></parent_chain><comment><author>orthoxerox</author><text>There&amp;#x27;s a series of blog posts by Oren Eini that shows that C# can be sufficiently fast even when you don&amp;#x27;t really optimize anything. Beating Redis in every benchmark is a whole another level, of course.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;ayende.com&amp;#x2F;blog&amp;#x2F;197412-B&amp;#x2F;high-performance-net-building-a-redis-clone-naively&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;ayende.com&amp;#x2F;blog&amp;#x2F;197412-B&amp;#x2F;high-performance-net-buildi...&lt;/a&gt;</text></comment>