<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Reflexiones y notas sobre el mundo de los servicios IT enfocados a soluciones de negocio. Reseñas sobre la elaboración de sistemas de información,valoración de frameworks, programación y opiniones sobre herramientas de desarrollo de aplicaciones &#187; memory</title>
	<atom:link href="http://www.esviable.es/tag/memory/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.esviable.es</link>
	<description>Reflexiones y notas sobre el mundo de los servicios IT enfocados a soluciones de negocio. Reseñas sobre la elaboración de sistemas de información,valoración de frameworks, programación y opiniones sobre herramientas de desarrollo de aplicaciones</description>
	<lastBuildDate>Sat, 22 May 2010 04:28:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Memory Profiling Go Languaje</title>
		<link>http://www.esviable.es/2010/02/27/memory-profiling-go-languaje/</link>
		<comments>http://www.esviable.es/2010/02/27/memory-profiling-go-languaje/#comments</comments>
		<pubDate>Sat, 27 Feb 2010 08:46:11 +0000</pubDate>
		<dc:creator>Efren</dc:creator>
				<category><![CDATA[Go Language]]></category>
		<category><![CDATA[Programacion]]></category>
		<category><![CDATA[memory]]></category>

		<guid isPermaLink="false">http://www.esviable.es/?p=178</guid>
		<description><![CDATA[If you are trying to debug a memory leak in your Go application, and need a way to determine which type is taking the most memory I.E a sorted list of (object type, total instances, total memory).
Runtime.MemStats doesn&#8217;t give details about the type, and goprof doesn&#8217;t seem to do memory profiling.
At this moment, the currente [...]]]></description>
			<content:encoded><![CDATA[<p>If you are trying to debug a memory leak in your Go application, and need a way to determine which type is taking the most memory I.E a sorted list of (object type, total instances, total memory).<br />
Runtime.MemStats doesn&#8217;t give details about the type, and goprof doesn&#8217;t seem to do memory profiling.</p>
<p>At this moment, the currente memory allocator only keeps track of whether or not the type can<br />
contain a pointer</p>
]]></content:encoded>
			<wfw:commentRss>http://www.esviable.es/2010/02/27/memory-profiling-go-languaje/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

