<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Memory Management 101</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx</link><description>Memory Management issues make up a considerable portion of the support incidents that we handle. At some point during the support incident we invariably engage in a discussion of Memory Management, Memory Tuning, the use of the infamous /3GB switch and</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>I'll never have to explain /3GB again...</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#710503</link><pubDate>Tue, 27 Mar 2007 14:53:24 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:710503</guid><dc:creator>Clive Watson's Weblog</dc:creator><description>&lt;p&gt;...I Hope! Well done to the performance team for their recent Windows Server articles, in particular&lt;/p&gt;
</description></item><item><title>re: Memory Management 101</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#718469</link><pubDate>Fri, 30 Mar 2007 18:05:27 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:718469</guid><dc:creator>jrich523</dc:creator><description>&lt;p&gt;Awesome post, goes over the basics very well but for those of you who like a bit more detail take a look at this.&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://msdn2.microsoft.com/en-us/library/ms810616.aspx"&gt;http://msdn2.microsoft.com/en-us/library/ms810616.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;keep em coming guys!&lt;/p&gt;
</description></item><item><title>Ask the Performance Team Blog</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#740623</link><pubDate>Mon, 09 Apr 2007 20:59:29 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:740623</guid><dc:creator>Carpe Diem: Flaphead.com @ Home</dc:creator><description>&lt;p&gt;No sure how I found this blog but its damm good. Check out these that I have been reading today! IE7&lt;/p&gt;
</description></item><item><title>Memory Management - Dude where's my RAM??</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#759052</link><pubDate>Fri, 13 Apr 2007 12:29:51 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:759052</guid><dc:creator>Ask the Performance Team</dc:creator><description>&lt;p&gt;Only a couple of years ago, desktop machines with 4GB of RAM were rare. Only high-end CAD designers and&lt;/p&gt;</description></item><item><title>Memory Management - Demystifying /3GB</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#899232</link><pubDate>Mon, 07 May 2007 13:25:33 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:899232</guid><dc:creator>Ask the Performance Team</dc:creator><description>&lt;p&gt;As promised - here's the long awaited post on the infamous /3GB switch. At least once a week we have&lt;/p&gt;</description></item><item><title>Memory Management - x86 Virtual Address Space</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#2068073</link><pubDate>Fri, 28 Sep 2007 17:35:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2068073</guid><dc:creator>Ask the Performance Team</dc:creator><description>&lt;p&gt;In previous posts, we've discussed the Basics of Memory Management , Pool Resources and of course the&lt;/p&gt;
</description></item><item><title>Troubleshooting Event ID 333 Errors</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#2288186</link><pubDate>Tue, 30 Oct 2007 16:14:14 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2288186</guid><dc:creator>Ask the Performance Team</dc:creator><description>&lt;p&gt;In previous posts we've discussed the basics of memory management including an overview of kernel and&lt;/p&gt;
</description></item><item><title>Understanding Bugchecks</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#2656652</link><pubDate>Tue, 18 Dec 2007 15:10:03 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2656652</guid><dc:creator>Ask the Performance Team</dc:creator><description>&lt;p&gt;Almost everyone that has ever used Windows has either heard of or experienced a bugcheck - the infamous&lt;/p&gt;
</description></item><item><title>Configuring Windows 2003 ( x64 ) for SQL Server</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#2717479</link><pubDate>Sun, 06 Jan 2008 23:49:26 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2717479</guid><dc:creator>Grumpy Old DBA</dc:creator><description>&lt;p&gt;There is an almost constant stream of posts on forums asking about configuration of SQL Server 2005 memory,&lt;/p&gt;
</description></item><item><title>re: Memory Management 101</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#3069212</link><pubDate>Wed, 11 Jun 2008 01:45:27 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3069212</guid><dc:creator>David Richter</dc:creator><description>&lt;p&gt;Goos summary on the memory manager. Process share memory as they reference a single instance of a DLL. Your web page points IPC and data transfer on disk (in bytes/ sec or quantity of bytes). Note that if an executable loads, only a piece of it loads, and only rerferenced part of the DLL needed loads : a vitualization. As features of the executable are used, then it is paged from disk. the memory manager has to calculate how much physical memory a process needs. It must involve an algorithm based on a prediction schedule obtained from a prefetch file, or something like that. Cool web site.&lt;/p&gt;</description></item><item><title>re: Memory Management 101</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#3089391</link><pubDate>Wed, 16 Jul 2008 06:28:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3089391</guid><dc:creator>Charles Kudla</dc:creator><description>&lt;p&gt; &amp;nbsp; Being a functional illiterate, I'm tired of low memory on the hard drive and warning messages. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Currently there is 60% RAM and 3% hard drive. &amp;nbsp;While looking for items to uninstall I notice multiple automatic updates and a gazillion uninstall files. &amp;nbsp;&lt;/p&gt;
&lt;p&gt; &amp;nbsp; When an updaye installs does it include previous updates, therefore, duplicating? &amp;nbsp;What is safe to uninstall and/or delete?&lt;/p&gt;</description></item><item><title>re: Memory Management 101</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#3211702</link><pubDate>Wed, 11 Mar 2009 19:15:32 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3211702</guid><dc:creator>driver dev guy</dc:creator><description>&lt;p&gt;hi hameed,&lt;/p&gt;
&lt;p&gt;you have explained about virtual address space, i would like to know who assigns this virtual address space of 4gb to the process.&lt;/p&gt;
&lt;p&gt;for eg : if i have 3 processes running , does it require to have 12 GB hard disk space ?&lt;/p&gt;</description></item><item><title>re: Memory Management 101</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#3211764</link><pubDate>Wed, 11 Mar 2009 20:50:16 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3211764</guid><dc:creator>Justin</dc:creator><description>&lt;p&gt;no, what its talking about is that each process has its own address range.. a virtual pool of memory that is 2GB in size... that 2 GB of virtual space is not allocated on physical memory until its used... so the process thinks it has 2G available to it, but lets say its only using 24MB.. that means only 24MB of physical memory is used.. the virtual memory manager (VMM) does a translations, or a mapping... of this virtual to physical for each process... also, each process has the same address range (00000000-7fffffff) so processA can be using address 00110011 in virtual memory.. but in physical memory it can be anything (you wont really know where it is in physical memory) and at the same time processB can also be using the address 00110011, which is the same virtual address, but on physical memory its different... its just a mapping.... translation... association... basically apps have no idea of physical memory, only virtual&lt;/p&gt;</description></item><item><title>re: Memory Management 101</title><link>http://blogs.technet.com/askperf/archive/2007/02/23/memory-management-101.aspx#3265894</link><pubDate>Sat, 18 Jul 2009 08:56:02 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3265894</guid><dc:creator>pablito lucban</dc:creator><description>&lt;p&gt;should there be any problem if i would up grade my 1gb ram to 2gb,my pc is hp pavillion dv6000 and its kind of slow starting specially when &amp;nbsp;i browse the internet.&lt;/p&gt;</description></item></channel></rss>