Allocate Virtual Memory
Tags:
- Virtual Memory
-
RAM
-
Memory
Last response: in Memory
Mr_Furball
June 5, 2014 4:35:09 PM
Mr_Furball
June 5, 2014 4:56:56 PM
Related resources
- Minecraft, allocate more memory to Java Virtual Machine (Windows 7) - Forum
- I have 8gb ram how much virtual memory i need to allocate? - Forum
- Need Help (Does using the onboard graphics to display the screen make the graphics card allocate more memory to Games?) - Forum
- Minecraft runs out of memory when i allocate 1 GB RAM instead of 545MB RAM default... - Forum
- How to allocate some SHARED MEMORY to DEDICATED MEMORY (ATI RADEON HD 4550) - Forum
Mr_Furball
June 5, 2014 5:16:26 PM
rgd1101 said:
for gaming, I would start with 512mb both min and max. if that doesn't work go to 1gb.You wouldn't want it to put too much data on the HDD virtual memory. Upgrade it 8 GB if you can.
By december I will upgrade it, but I don't actually know what changes by changing the virtual memory, because I was having some issues like extremely high disk activity, 100% activity, some users were having the same bug in windows 8, so in a website they said the best way is to put your whole virtual virtual memory in the initial
-
Reply to Mr_Furball
m
0
l
larger virtual memory mean more space for software to work with, but also mean the os might try to put more stuff in it too(high disk activity). Unless the games is crashing with low memory error, I would set it low. but since you only got 4GB right now, try 512mb then 1GB, then 1.5gb. etc and try not to run anything else when you gaming.
-
Reply to rgd1101
m
0
l
Mr_Furball
June 5, 2014 6:19:16 PM
rgd1101 said:
larger virtual memory mean more space for software to work with, but also mean the os might try to put more stuff in it too(high disk activity). Unless the games is crashing with low memory error, I would set it low. but since you only got 4GB right now, try 512mb then 1GB, then 1.5gb. etc and try not to run anything else when you gaming.Sorry man, one more thing. Should I set 512mb on initial and maximum, like, always the same number in both? Should I leave to the system to choose? When I have 8gb how much should I set? And if I have to run more programs? Sorry for all the questions
-
Reply to Mr_Furball
m
0
l
Mr_Furball
June 5, 2014 6:34:09 PM
rgd1101 said:
yes always the same number on both. don't let the system choose.when you have 8GB, set it to the min(I think is like 16MB). unless some old programs that you are using required more.
Same rule, only add more to it only if it complain about running out of memory.
Oh okay, but one doubt, that obviously is not only what the system will use, so what is it for? If I set on mininum with 8gb won't compromise the games right, and why less if I have more RAM?
-
Reply to Mr_Furball
m
0
l
It was useful when RAM was expensive and not as much space(4GB max on 32bit os) compare to HDD. The os write out ram stuff that it think you are not using to the disk so you can run more apps at the same time, down side is that HDD is slow.
I haven't see a games that required more or at 8GB.
Unless you are doing video conversion or something. 8GB is plenty.
I haven't see a games that required more or at 8GB.
Unless you are doing video conversion or something. 8GB is plenty.
-
Reply to rgd1101
m
0
l
Mr_Furball
June 5, 2014 7:05:15 PM
13444781,0,600985 said:
It was useful when RAM was expensive and not as much space(4GB max on 32bit os) compare to HDD. The os write out ram stuff that it think you are not using to the disk so you can run more apps at the same time, down side is that HDD is slow.I haven't see a games that required more or at 8GB.
Unless you are doing video conversion or something. 8GB is plenty.[/quot
Yes, Watch Dogs recommends 8gb of RAM, but do you believe in these recommended specs and minimum? Anyway I set to 512mb thanks
-
Reply to Mr_Furball
m
0
l
Best solution
It is advisable that the minimum page file size be set to no less than 1 gigabyte. This ensures that Windows has space to write crash dumps in the event of a kernel failure.
In most cases, a page file size of between one and one and a half times the installed SDRAM (physical memory) is appropriate. If you have an SSD you may wish to ensure that the page file is only enabled on an accompanying mechanical drive.
Operating systems have very finely tuned page replacement policies. The existence of a sizeable page file allows infrequently used services and processes to be ejected from the physical address space without terminating them. This allows the operating system to overcommit virtual memory to applications and use the scarce physical memory on demand for applications that actually need it (as opposed to simply allocating it and not releasing it), or as a cache to speed up file system access.
Demand paging is not solely designed to expand the amount of instantaneous memory available to all processes and waiting until the computer is out of memory to increase it is not a sane page file management policy. If you have a substantial amount of unused hard disk space, let the operating system manage the page file size. It knows what it's doing.
In most cases, a page file size of between one and one and a half times the installed SDRAM (physical memory) is appropriate. If you have an SSD you may wish to ensure that the page file is only enabled on an accompanying mechanical drive.
Operating systems have very finely tuned page replacement policies. The existence of a sizeable page file allows infrequently used services and processes to be ejected from the physical address space without terminating them. This allows the operating system to overcommit virtual memory to applications and use the scarce physical memory on demand for applications that actually need it (as opposed to simply allocating it and not releasing it), or as a cache to speed up file system access.
Demand paging is not solely designed to expand the amount of instantaneous memory available to all processes and waiting until the computer is out of memory to increase it is not a sane page file management policy. If you have a substantial amount of unused hard disk space, let the operating system manage the page file size. It knows what it's doing.
-
Reply to Pinhedd
Share
Mr_Furball
June 5, 2014 8:55:52 PM
Pinhedd said:
It is advisable that the minimum page file size be set to no less than 1 gigabyte. This ensures that Windows has space to write crash dumps in the event of a kernel failure.In most cases, a page file size of between one and one and a half times the installed SDRAM (physical memory) is appropriate. If you have an SSD you may wish to ensure that the page file is only enabled on an accompanying mechanical drive.
Operating systems have very finely tuned page replacement policies. The existence of a sizeable page file allows infrequently used services and processes to be ejected from the physical address space without terminating them. This allows the operating system to overcommit virtual memory to applications and use the scarce physical memory on demand for applications that actually need it (as opposed to simply allocating it and not releasing it), or as a cache to speed up file system access.
Demand paging is not solely designed to expand the amount of instantaneous memory available to all processes and waiting until the computer is out of memory to increase it is not a sane page file management policy. If you have a substantial amount of unused hard disk space, let the operating system manage the page file size. It knows what it's doing.
Alright, don't have an SSD, just one 1TB with 300gb (220 avaliable now on disk C
and 600gb on the D: for the games (400 avaliable). So I will leave for the system to manage it, because I was having this 100% disk activity, some sort of bug I don't know. But your explation was pretty good but sorry, since I don't know a lot about memory and all ( and a little retarded) I didn't get all the tips -
Reply to Mr_Furball
m
0
l
Mr_Furball said:
Pinhedd said:
It is advisable that the minimum page file size be set to no less than 1 gigabyte. This ensures that Windows has space to write crash dumps in the event of a kernel failure.In most cases, a page file size of between one and one and a half times the installed SDRAM (physical memory) is appropriate. If you have an SSD you may wish to ensure that the page file is only enabled on an accompanying mechanical drive.
Operating systems have very finely tuned page replacement policies. The existence of a sizeable page file allows infrequently used services and processes to be ejected from the physical address space without terminating them. This allows the operating system to overcommit virtual memory to applications and use the scarce physical memory on demand for applications that actually need it (as opposed to simply allocating it and not releasing it), or as a cache to speed up file system access.
Demand paging is not solely designed to expand the amount of instantaneous memory available to all processes and waiting until the computer is out of memory to increase it is not a sane page file management policy. If you have a substantial amount of unused hard disk space, let the operating system manage the page file size. It knows what it's doing.
Alright, don't have an SSD, just one 1TB with 300gb (220 avaliable now on disk C
and 600gb on the D: for the games (400 avaliable). So I will leave for the system to manage it, because I was having this 100% disk activity, some sort of bug I don't know. But your explation was pretty good but sorry, since I don't know a lot about memory and all ( and a little retarded) I didn't get all the tipsModern operating systems are the culmination of over 50 years of research and development. Virtual memory management, including the page replacement policy (also called swapping, the procedure that the operating system uses to determine what memory to eject from the physical address space and eject to a backing store such as a hard disk) is one aspect that is about as optimal as it can be and the defaults are almost always adequate. The only reason to change it that I can think of is if the user has an SSD and wishes to prevent the OS from populating it with a hefty page file.
In software optimization we follow what is known as the 80/20 rule (also sometimes expressed as the 90/10 rule), which states that in the common case a program will spend 80% of its runtime within the same 20% of the code. This implies that optimization should be focused on this 20% of the code. It also implies that the other 80% of the code may include code that is rarely used, if ever. Code and data that is only used during startup, or shutdown, or during a failure is unlikely to be used during the common case. A smart programmer knows this and will ensure that non-critical components are unloaded if possible. A lazy programmer doesn't and instead lets the operating system and/or application runtime do all of the work instead. The page replacement policy attempts to seek out memory pages (a 4KiB chunk of memory on most machines) that are infrequently used and kick them out of physical memory so that the memory can instead be used for more useful tasks, such as the operating systems own internal file system cache or another application. If an application references a virtual memory address that does not have a corresponding physical address (meaning that the memory has either been paged-out to a backing store, or was never loaded into physical memory in the first place) the operating system will load it back in before continuing.
-
Reply to Pinhedd
m
0
l
Mr_Furball
June 6, 2014 11:23:29 AM
Pinhedd said:
Mr_Furball said:
Pinhedd said:
It is advisable that the minimum page file size be set to no less than 1 gigabyte. This ensures that Windows has space to write crash dumps in the event of a kernel failure.In most cases, a page file size of between one and one and a half times the installed SDRAM (physical memory) is appropriate. If you have an SSD you may wish to ensure that the page file is only enabled on an accompanying mechanical drive.
Operating systems have very finely tuned page replacement policies. The existence of a sizeable page file allows infrequently used services and processes to be ejected from the physical address space without terminating them. This allows the operating system to overcommit virtual memory to applications and use the scarce physical memory on demand for applications that actually need it (as opposed to simply allocating it and not releasing it), or as a cache to speed up file system access.
Demand paging is not solely designed to expand the amount of instantaneous memory available to all processes and waiting until the computer is out of memory to increase it is not a sane page file management policy. If you have a substantial amount of unused hard disk space, let the operating system manage the page file size. It knows what it's doing.
Alright, don't have an SSD, just one 1TB with 300gb (220 avaliable now on disk C
and 600gb on the D: for the games (400 avaliable). So I will leave for the system to manage it, because I was having this 100% disk activity, some sort of bug I don't know. But your explation was pretty good but sorry, since I don't know a lot about memory and all ( and a little retarded) I didn't get all the tipsModern operating systems are the culmination of over 50 years of research and development. Virtual memory management, including the page replacement policy (also called swapping, the procedure that the operating system uses to determine what memory to eject from the physical address space and eject to a backing store such as a hard disk) is one aspect that is about as optimal as it can be and the defaults are almost always adequate. The only reason to change it that I can think of is if the user has an SSD and wishes to prevent the OS from populating it with a hefty page file.
In software optimization we follow what is known as the 80/20 rule (also sometimes expressed as the 90/10 rule), which states that in the common case a program will spend 80% of its runtime within the same 20% of the code. This implies that optimization should be focused on this 20% of the code. It also implies that the other 80% of the code may include code that is rarely used, if ever. Code and data that is only used during startup, or shutdown, or during a failure is unlikely to be used during the common case. A smart programmer knows this and will ensure that non-critical components are unloaded if possible. A lazy programmer doesn't and instead lets the operating system and/or application runtime do all of the work instead. The page replacement policy attempts to seek out memory pages (a 4KiB chunk of memory on most machines) that are infrequently used and kick them out of physical memory so that the memory can instead be used for more useful tasks, such as the operating systems own internal file system cache or another application. If an application references a virtual memory address that does not have a corresponding physical address (meaning that the memory has either been paged-out to a backing store, or was never loaded into physical memory in the first place) the operating system will load it back in before continuing.
Damn, that was a hell of an explanation, thank you man! I wish I could say more
-
Reply to Mr_Furball
m
0
l
Related resources
- How do you allocate graphics memory on asus m5a78l-m/usb3 Forum
- Mac Partition, how to allocate more memory to windows Forum
- How to allocate more video memory in bios Forum
- Video memory n/a shared video memory n/a how to allocate memory to the video dis Forum
- How allocate memory to video on Compaq Presario CQ61-315SQ Forum
- Solved12GB DDR3 RAM, 4GB auto allocated to virtual RAM Forum
- Programs running low on system memory - How can I allocate? Forum
- SolvedIncreasing virtual memory Forum
- SolvedHow to reduce the virtual memory? Forum
- SolvedWindows 7 Virtual memory Sizes Forum
- Solvedpagefile on windows 8.1 and virtual memory Forum
- Solvedvirtual memory sizes Forum
- SolvedGame Development Environment - Virtual Memory on SSD | Fast HDD worth it? | SATA 3 Expansion Card | Memory Frequency @ CPU OC Forum
- SolvedDoes Virtual Memory Speed Up My Laptop Forum
- Solvedwhat is the difference between hardware memory, software memory and virtual memory? Forum
- More resources
Read discussions in other Memory categories
!