Sponsored Content
Full Discussion: physical memory
Operating Systems Solaris physical memory Post 302204949 by jayaramanit on Friday 13th of June 2008 02:36:37 AM
Old 06-13-2008
physical memory

what is the command to find the physical memory in soalris OS and how to find whether paging is happening or not ?
 

10 More Discussions You Might Find Interesting

1. Programming

Physical Memory

Hi, My problem is next.... How can I work with physical memory in the Unix FreeBSD 2.2 or hight? What is the "mem" & "kmem" drivers? P.S./ writing device driver for UNIX FreeBSD 2.2 :D (2 Replies)
Discussion started by: Alex_T
2 Replies

2. UNIX for Dummies Questions & Answers

physical memory

It is just a general question....is there a limit on the memory? I am looking into a process to store image files on the unix server which will be accessed by the application, and I just wonder if there is any limit regarding the physical or virtual memory. I am very new to unix, so thanks for... (1 Reply)
Discussion started by: cchien
1 Replies

3. Shell Programming and Scripting

get physical and virtual memory

What command can i use to get the physical and virtual memory of a database? (7 Replies)
Discussion started by: tads98
7 Replies

4. UNIX for Advanced & Expert Users

vmstat -P (physical memory)

vmstat -P commands gives me an output as shown at the end of this message. my first question is about the difference between "total physical memory" and "total physical memory use" "Total Physical Memory" -"Total Physical Memory Use" 524288 pages-524026 pages= 262 pages does it mean... (0 Replies)
Discussion started by: gfhgfnhhn
0 Replies

5. Solaris

How to check physical memory

HI Please help me how to check the physical memory, model name and hardisk information. (5 Replies)
Discussion started by: jeelans
5 Replies

6. Solaris

How to find Total and Free Physical Memory and Logical Memory in SOLARIS 9

Hi, Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:- 1. Total Physical Memory in the system(total RAM). 2. Available Physical Memory(i.e. RAM Usage) 3. Total (Logical) Memory in the system 4. Available (Logical) Memory. I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies

7. Solaris

restrcit physical memory with zone.max-locked-memory

Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd (1 Reply)
Discussion started by: fugitive
1 Replies

8. AIX

Physical Memory expansion

IBM says we cannot expand our physical memory on our 570's without upgrading all the existing DIMMS since all slots are currently full. Is it really so difficult for IBM to build servers that leave a couple vacant slots for future expansion? A technical explanation would be greatly appreciated.... (2 Replies)
Discussion started by: 1computerman
2 Replies

9. UNIX for Dummies Questions & Answers

random Physical memory dump

I am currently running unix open server 6.0 on a Dell Power Edge R720. The system will be running fine when the blue screen appears and states the system has performed a physical memory dump in # of ticks. I reboot the system and all looks well. Running diagnostics does not show anything wrong. The... (1 Reply)
Discussion started by: rformt
1 Replies

10. Solaris

Physical memory calculation

Below is Physical Memory result : -bash-3.00$ prtconf | grep "Memory size" Memory size: 36854 Megabytes -bash-3.00$ vmstat 1 2 | tail -1 0 0 0 28220616 1318888 15 143 0 0 0 0 0 253 2 15 0 5215 14989 5917 7 0 93 and the script i have to calculate this in Percentage is : #!/bin/sh... (3 Replies)
Discussion started by: mjoshi010207
3 Replies
desfree_pct(5)							File Formats Manual						    desfree_pct(5)

NAME
desfree_pct - sets the lower bound before paging daemon starts stealing pages, specified as a percentage of available physical memory VALUES
Failsafe Default Allowed values Must not be greater than (see lotsfree_pct(5)). DESCRIPTION
is a tunable parameter to set the lower bound before the paging daemon start stealing pages. It is specified as a percentage of physical memory available after boot. must be a positive integer between 0 and 30 and must be equal to or less than (see lotsfree_pct(5)). Trying to set higher than results in The paging daemon in HP-UX acts on a "two hand" model. The daemon runs at least once a second, with one part marking pages of virtual address space as "unused". If the page is referenced before this "aging" hand returns, it will be marked as "used" again. Another section of the daemon, the "steal" hand follows the age hand (the distance between them varies in a well bounded range) and processes pages which are still marked "unused", since needed or frequently accessed pages would have a high likelihood of being referenced in the gap between the hands. Exactly how the steal hand treats the pages still marked as "unused" depends on the comparison of free system physical memory and three paging parameters: and Between and is a periodically re-calculated and, hence floating, threshold known as Thus and are the upper and lower bounds between which moves. is an expression of how much the system maintains, expressed in percentage terms (percentage of physical memory available after boot). o If is greater than the system's memory availability is in good shape. The steal hand does nothing as a lot of memory is still available on the system, so there is no need to "steal' a page that might be needed soon. o In the more common case, when is lower than (but higher than the steal hand will begin to steal pages that have remained unreferenced from when the age hand last marked them. "Stealing" a page refers to the process of freeing the page from being allocated for a partic- ular virtual page and making it available for general allocation again. If falls below but is still more than memory availability is still in reasonable shape, but the paging daemon begins stealing pages more aggressively, including putting lower priority processes to sleep to free up their memory. o When is less than free memory in the system is getting more critical; the paging daemon begin deactivating low priority processes, in other words, swapping out pages to the swap device. Since the exact memory topography varies widely across supported platforms, the paging parameters and are tunable to allow for cases where the default values are insufficient, or where the system administrator requires more control over the actions of the paging daemon. In general, however, the automatic calculation performed by default should suffice for most systems. is a system calculated value. Who Is Expected to Change This Tunable? Anyone with super-user privileges. Restrictions on Changing Changes to this tunable take effect immediately. When Should the Value of This Tunable Be Raised? This tunable should be raised on systems where system memory is critical for short-term, high priority processes, but is being held by low- priority, long running processes. For example, when one web server is forking off per-connection threads while 50 RCS clients run in the background. Increasing (and hence would raise the likelihood of the low-priority processes being put to sleep, allowing the high-priority processes a chance to acquire the pages that were previously allocated to the former. What are the Side Effects of Raising the Value? As increases, more low priority processes might be forced to sleep. Depending on what these processes are actually doing, this may not be the right approach. When Should the Value of This Tunable Be Lowered? Raising too high can impair performance of lower priority processes as previously described. In addition, raising and increases system overhead (it takes time to swap a page to disk), and should be weighed carefully against the need or desire to keep a large pool of physical memory unused. Some free memory is essential, a moderate amount is probably good, a lot of free memory just sitting idle is a waste. If the available physical memory on the machine seems generous and heavy swapping is occurring, lowering and/or will increase memory usage but decrease swapping overhead. What are the Side Effects of Lowering the Value? More physical memory will be in use before processes are put to sleep to try to reclaim their frames. What Other Tunable Values Should Be Changed at the Same Time? should be considered when modifying for reasons previously described above. acts as a firm upper bound to so attempting to set above is meaningless and will result in an error. See lotsfree_pct(5). Notes Starting with HP-UX 11i Version 2, HP recommends the use of to specify the lower bound for the paging daemon. ERRORS
Memory resource management infrastructure is busy. Please try later. Attempting to set above An invalid value is entered that is not an integer between 0 and 30, such as an negative number. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
lotsfree_pct(5). Tunable Kernel Parameters desfree_pct(5)
All times are GMT -4. The time now is 02:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy