|
|
Sponsored Content
Operating Systems
AIX
Memory trouble
Post 302319531 by septima.pars on Monday 25th of May 2009 12:57:46 PM
05-25-2009
|
|
10 More Discussions You Might Find Interesting
1. HP-UX
Refer from title:
How can i get memory used or anything that can show memory from sar file
example on solaris:-
we can use sar with option to show memory used at time that sar crontab run.
on HP-UX, it not has option to see memory used. But i think it may be have some parameter or some... (1 Reply)
Discussion started by: panithat
1 Replies
2. Solaris
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
3. Programming
Hi,
I'm trying to learn how to manage memory when I have to deal with lots of data.
Basically I'm indexing a huge file (5GB, but it can be bigger), by creating tables that
holds offset <-> startOfSomeData information. Currently I'm mapping the whole file at
once (yep!) but of course the... (1 Reply)
Discussion started by: emitrax
1 Replies
4. Solaris
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
5. UNIX for Dummies Questions & Answers
Hello,
I am trying to free memory allocation after EOF from keyboard is detected (ctrl+D) in a C program. I've written a small program to replicate my problem:
int main(int argc, char *argv) {
char *line;
line = (char*)malloc(sizeof(char)*(512));
line = fgets(line, 512,... (1 Reply)
Discussion started by: oddworld
1 Replies
6. Programming
Hello,
I am trying to free memory allocation after EOF from keyboard is detected (ctrl+D) in a C program. I've written a small program to replicate my problem:
int main(int argc, char *argv) {
char *line;
line = (char*)malloc(sizeof(char)*(512));
line = fgets(line, 512,... (10 Replies)
Discussion started by: oddworld
10 Replies
7. UNIX for Advanced & Expert Users
I was running a program and it stopped and showed "Out of Memory!". at that time, the RAM used by this process is around 4G and the free memory size of the machine is around 30G. Does anybody know what maybe the reason? this program is written with Perl. the OS of the machine is Solaris U8. And I... (1 Reply)
Discussion started by: lilili07
1 Replies
8. Solaris
Hello solaris experts,
Being new to solaris containers, from Linux, feeling difficulty in understanding certain concepts. Hope somebody can help me here.
I understand that, & some questions ....
Locked memory -- memory which will not be swapped out at any cause.
is this for... (0 Replies)
Discussion started by: thegeek
0 Replies
9. Solaris
Hi Experts,
Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing.
Why memory utilization on solaris always looks high?
I have statement about memory on solaris, is this true:
Memory in solaris is used for... (4 Replies)
Discussion started by: edydsuranta
4 Replies
10. AIX
memory is more than 80% how will u trouble shoot it? (1 Reply)
Discussion started by: ramraj731
1 Replies
LEARN ABOUT HPUX
strmsgsz
STRMSGSZ(5) File Formats Manual STRMSGSZ(5) NAME
STRMSGSZ - maximum size of streams message data (bytes) VALUES
Failsafe Default Allowed values Recommended values DESCRIPTION
This tunable limits the number of bytes of message data that can be inserted by or in the data portion of any streams message on the sys- tem. If the tunable is set to zero, there is no limit on how many bytes can be placed in the data segment of the message. returns if the buffer being sent is larger than the current value of segments the data into multiple messages. Who Is Expected to Change This Tunable? Any customer. Restrictions on Changing Changes to this tunable take effect at next reboot. When Should the Value of This Tunable Be Raised? The tunable should be increased by any customer if the customer's STREAMS module/driver(s) require a longer message size in the data por- tion than the current value. What Are the Side Effects of Raising the Value of This Tunable? The kernel will use more memory. During low memory situations, it may bring down system performance due to frequent swapping. When Should the Value of This Tunable Be Lowered? The tunable could be lowered by any customer if the customer's STREAMS module/driver(s) do not require a longer message size in the data portion than the current value. What Are the Side Effects of Lowering the Value of This Tunable? Possible improper functioning in any of the STREAMS module/driver(s). Possible performance degradation, particularly in networking. What Other Tunable Should Be Changed at the Same Time as This One? None. 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. Tunable Kernel Parameters STRMSGSZ(5)