<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance on The Lone C++ Coder's Blog</title><link>https://www.lonecpluspluscoder.com/tags/performance/</link><description>Recent content in Performance on The Lone C++ Coder's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 14 Dec 2014 21:39:41 +0000</lastBuildDate><atom:link href="https://www.lonecpluspluscoder.com/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Making git work better on Windows</title><link>https://www.lonecpluspluscoder.com/2014/12/14/making-git-work-better-windows/</link><pubDate>Sun, 14 Dec 2014 21:39:41 +0000</pubDate><author>Timo Geusch</author><guid>https://www.lonecpluspluscoder.com/2014/12/14/making-git-work-better-windows/</guid><description>&lt;p&gt;In a &lt;a href="https://www.lonecpluspluscoder.com/2014/03/12/improving-the-performance-of-git-for-windows/" title="Improving the performance of Git for Windows"&gt;previous blog post&lt;/a&gt; I explained how you can substantially improve the performance of git on Windows updating the underlying SSH implementation. This performance improvement is very worthwhile in a standard Unix-style git setup where access to the git repository is done using ssh as the transport layer. For a regular development workstation, this update works fine as long as you keep remembering that you need to check and possibly update the ssh binaries after every git update.&lt;/p&gt;</description></item><item><title>Improving the performance of Git for Windows</title><link>https://www.lonecpluspluscoder.com/2014/03/12/improving-the-performance-of-git-for-windows/</link><pubDate>Wed, 12 Mar 2014 19:35:04 +0000</pubDate><author>Timo Geusch</author><guid>https://www.lonecpluspluscoder.com/2014/03/12/improving-the-performance-of-git-for-windows/</guid><description>&lt;p&gt;Admittedly I&amp;rsquo;m  not the biggest fan of &lt;a href="http://git-scm.com/"&gt;git&lt;/a&gt; - I prefer &lt;a href="http://mercurial.selenic.com/"&gt;Mercurial&lt;/a&gt; - but we&amp;rsquo;re using it at work and it does a good job as a DVCS. However, we&amp;rsquo;re mostly a Windows shop and the out of the box performance of &lt;a href="http://msysgit.github.io/"&gt;Git for Windows&lt;/a&gt; is anything but stellar when you are using ssh as the transport for git. That&amp;rsquo;s not too much bother with most of our repos but we have a couple of fairly big ones and clone performance with those matters.&lt;/p&gt;</description></item><item><title>Sometimes, std::set just doesn't cut it from a performance point of view</title><link>https://www.lonecpluspluscoder.com/2010/12/12/sometimes-stdset-just-doesnt-cut-it-from-a-performance-point-of-view/</link><pubDate>Sun, 12 Dec 2010 18:45:33 +0000</pubDate><author>Timo Geusch</author><guid>https://www.lonecpluspluscoder.com/2010/12/12/sometimes-stdset-just-doesnt-cut-it-from-a-performance-point-of-view/</guid><description>&lt;p&gt;A piece of code I recently worked with required data structures that hold unique, sorted data elements. The requirement for the data being both sorted and unique came from it being fed into std::set_intersection() so using an std::set seemed to be an obvious way of fulfilling these requirements. The code &lt;em&gt;did&lt;/em&gt; fulfill all the requirements but I found the performance somewhat wanting in this particular implementation (Visual Studio 2008 with the standard library implementation shipped by Microsoft). The main problem was is that this code is extremely critical to the performance of the application and it simply wasn&amp;rsquo;t fast enough at this point.&lt;/p&gt;</description></item></channel></rss>