﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on Optimizations gone wild, O(N!) memory leaks</title><description>Alois,
That is a great project, I am looking forward to digging into that.</description><link>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment7</link><guid>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment7</guid><pubDate>Tue, 18 Dec 2012 22:08:36 GMT</pubDate></item><item><title>Alois Kraus commented on Optimizations gone wild, O(N!) memory leaks</title><description>For regression testing you could WMemoryProfiler (https://wmemoryprofiler.codeplex.com/). It is free. You can download the latest sources to get it up and running. 
</description><link>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment6</link><guid>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment6</guid><pubDate>Tue, 18 Dec 2012 20:51:44 GMT</pubDate></item><item><title>Ayende Rahien commented on Optimizations gone wild, O(N!) memory leaks</title><description>Paul,
No, because each time it will issue a set of additional batches from the start of the next one, and so on. We will miss those, and issue another set, and so on.</description><link>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment5</link><guid>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment5</guid><pubDate>Mon, 17 Dec 2012 12:30:10 GMT</pubDate></item><item><title>Joseph Daigle commented on Optimizations gone wild, O(N!) memory leaks</title><description>Yeah, it's (N^2)/2 not N!. You're taking the summation of N...1, not the product.</description><link>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment4</link><guid>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment4</guid><pubDate>Mon, 17 Dec 2012 12:27:50 GMT</pubDate></item><item><title>paul commented on Optimizations gone wild, O(N!) memory leaks</title><description>Isn't it a O(n^2) leak?</description><link>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment3</link><guid>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment3</guid><pubDate>Mon, 17 Dec 2012 12:13:39 GMT</pubDate></item><item><title>Ayende Rahien commented on Optimizations gone wild, O(N!) memory leaks</title><description>Harry,
No, we don't.
We use dog fooding for those sort of issues.</description><link>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment2</link><guid>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment2</guid><pubDate>Mon, 17 Dec 2012 11:32:12 GMT</pubDate></item><item><title>Harry McIntyre commented on Optimizations gone wild, O(N!) memory leaks</title><description>Do you have automated tests for catching memory issues, and if so, how do they work?</description><link>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment1</link><guid>http://ayende.com/160292/optimizations-gone-wild-o-n-memory-leaks#comment1</guid><pubDate>Mon, 17 Dec 2012 11:27:38 GMT</pubDate></item></channel></rss>