Talk:Commit charge

message: This article first needs to be tidied up. It's pretty messy, and it has information in one paragraph when it should be in another. --Gary King 17:32, 11 December 2005 (UTC)
replies: text: Absolutely correct.  I just did a "brain dump" to get the facts down quickly (and correct errors in the previous version) but haven't had time to get back to it.  It's  tough to provide a useful explanation of what "commit charge" really is without explaining most of the Windows memory management subsystem... Jeh 11:36, 12 December 2005 (UTC)
thread_title:  Tidy it up first 

message: Moved here from comments placed in the article by an anonymous contributor, 64.203.165.227:
: It'd be nice if the author of this page would add what units these values are in. Is it megabytes, kilobytes, etc... 
My response: The display itself shows that the units are K (kilobytes). Is something more needed?  Jeh (talk) 02:09, 30 January 2008 (UTC)
thread_title:  Units 

message: :Image:Windows Task Manager Performance.png is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If there is  other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page.  Note that any fair use images lacking such an explanation can be deleted one week after being tagged, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.
BetacommandBot (talk) 03:17, 12 February 2008 (UTC)
thread_title: Fair use rationale for Image:Windows Task Manager Performance.png

message: The article does not explain why a measure of virtual memory is called "commit charge." That is not obvious, at least not to me. Dratman (talk) 03:37, 10 August 2008 (UTC)
replies: text: Really? I thought the term obviously derived from being the memory the OS is charged (entrusted) with that is committed (VM term meaning not backed by a file and not re-creatable). The English is a bit obscure, but in something like a column heading, concise is more important than everyday. 79.123.73.149 (talk) 23:03, 10 April 2012 (UTC)
thread_title:  What is the origin of the phrase? 

message: I found this article to be unclear.  It does not explain what "backing store" is, nor what "pagefile-backed" means.  In general, it seems to assume a fair amount of knowledge that is probably not common.  I realize that a thorough discussion of computer memory and operating systems is not appropriate here, but some of these terms could be fleshed out a little bit, or linked to explanations elsewhere (though the virtual address space article has similar problems), without exploding the length of the article.  Images of the Task Manager dialog box would also be helpful. Uunter (talk) 20:26, 6 February 2009 (UTC)
replies: text: Hm, well, actually, it uses hard drive space long before it runs out of RAM. (But that doesn't really have anything to do with "commit charge".) To completely explain all of this requires a complete description of how Windows implements virtual memory. This is a subject of a 200-page chapter in the Sixth Edition of Windows Internals. It isn't easy to pluck a concept like "commit charge" out of all that and explain it in a self-contained article. I'm not saying the article can't be or shouldn't be improved, but every time I've started to try it the result has just expanded beyond hope. I'm sure people will keep trying. Jeh (talk) 23:15, 21 May 2015 (UTC)
thread_title:  Undefined terms 

message: post a common rule how big or small the pagefile.sys should be. the articel should be a bit more practical--User1973 (talk) 17:40, 28 June 2009 (UTC)
replies: text: Please see WP:NOT.  In particular Wikipedia is not a how-to manual. Jeh (talk) 02:40, 29 June 2009 (UTC)
thread_title:  post a common rule how big the pagefile.sys should be 

message: The article does not reflect the version of Task manager included in Windows 7 which, for example, under Physical memory lists Total, Cached, Available and Free, while the article refers to Total, Limit and Peak. Silver hr (talk) 13:37, 27 January 2011 (UTC)
replies: text: Win7 Task manager in the "Physical Memory" section in the Performance tab is not showing you "commit charge" at all, but rather physical memory (RAM). Commit charge is a category of virtual memory, not physical.   Jeh (talk) 10:11, 4 April 2011 (UTC)
thread_title:  Some information outdated 

message: The article mentions that increasing the page file size is one way to increase the commit limit. There is another: on systems with Hot-Add Memory support, inserting additional DIMMs will also increase the commit limit, as the amount of physical RAM increases. [Alex Ionescu] --67.169.39.64 (talk) 14:13, 7 April 2012 (UTC)
thread_title:  Increasing Commit Limit