Sponsored Content
Full Discussion: Slower slower dead
Top Forums UNIX for Dummies Questions & Answers Slower slower dead Post 6915 by Neo on Friday 14th of September 2001 11:10:03 PM
Old 09-15-2001
Processes that have memory leaks will be using lots of memory and not releasing the memory to other processes. This often occurs when a process allocates memory (sometimes in a branch of the process that is done repeatedly) and the allocation is not released.

If you have your system set up for swap; then you will notice that your system begins to swap, slowing things down. If you don't have enough swap space (or any swap) things will grind to a halt.

Too many processes can also slow things down, but this is not a memory leaks, just too little memory!!!

How much RAM do you have? How much swap space? What are the top memory-hog-processes on your system?
 

8 More Discussions You Might Find Interesting

1. Programming

TCP/IP send getting slower

Hi, We have developed a server program using TCP/IP Communication to communicate with another client program. After running for some days we find the TCP/IP connection from the server program is getting slower ie, the messages are not send quickly to the client. What i mean to say is since the... (0 Replies)
Discussion started by: rajesh_puru
0 Replies

2. UNIX for Advanced & Expert Users

TCP/IP Connection getting slower...

Hi, We have developed a server program using TCP/IP Communication to communicate with another client program. After running for some days we find the TCP/IP connection from the server program is getting slower. What i mean to say is since the send() function in the server program (it is... (2 Replies)
Discussion started by: rajesh_puru
2 Replies

3. Solaris

Why is restore slower than backup?

After my big disaster, I'm restoring from tape on my Sun box. This is the second time I've used 'ufsrestore' with this DEC TZ88 SCSI DLT drive. The last time was for a migration from one box to another. Both the last time and this time, the restore has taken a hell of a lot longer than the... (4 Replies)
Discussion started by: deckard
4 Replies

4. UNIX for Advanced & Expert Users

Why is cut slower than awk?

Hi all, for test reasons I tried the following two one-liners: time awk '{print $4}' T_64xSC_128RW_K500.dat > /dev/nulland time cut -d" " -f6 T_64xSC_128RW_K500.dat > /dev/nullThe file contains approx. 250k lines. awk does it in 0.15 secs (real), cut in 0.44. The user time has about the... (3 Replies)
Discussion started by: BandGap
3 Replies

5. Linux

GCC compiles a lot slower than it should

Hello everyone, i'm having a problem compiling an application i'm developing. For a month, while developing, i did lots of compilations to test it. While compiling, i noticed gcc did it pretty slow, but gave it no importance. I'm using ubuntu 10.04 32bits, and my pc has: - Dual core intel... (1 Reply)
Discussion started by: adadon
1 Replies

6. What is on Your Mind?

Usenet is dead

On servers i check there seems to be no news at all. (3 Replies)
Discussion started by: Action
3 Replies

7. Shell Programming and Scripting

sed is dead

Hello everybody, I'm new to bash scripting (and scripting in general) but I'm making decent progress in the hands-on solutions I need... I've encountered a problem that seemed very simple to me at first, but had me going on for hours. Maybe you can help me. Say I have an input text file like... (2 Replies)
Discussion started by: origamisven
2 Replies

8. Solaris

Job Run Slower using Autosys than running through terminal

Hi All, We run Many jobs evryday using Autosys. Sometimes due to various reason we got to run the job from terminal as well (using nohup). We observed that the job running through terminal(nohup) takes much less time then the autosys (for same job). What can be the possible reason for such... (1 Reply)
Discussion started by: kg_gaurav
1 Replies
PROTECT(1)						    BSD General Commands Manual 						PROTECT(1)

NAME
protect -- protect processes from being killed when swap space is exhausted SYNOPSIS
protect [-i] command protect [-cdi] -g pgrp | -p pid DESCRIPTION
The protect command is used to mark processes as protected. The kernel does not kill protected processes when swap space is exhausted. Note that this protected state is not inherited by child processes by default. The options are: -c Remove protection from the specified processes. -d Apply the operation to all current children of the specified processes. -i Apply the operation to all future children of the specified processes. -g pgrp Apply the operation to all processes in the specified process group. -p pid Apply the operation to the specified process. command Execute command as a protected process. Note that only one of the -p or -g flags may be specified when adjusting the state of existing processes. EXIT STATUS
The protect utility exits 0 on success, and >0 if an error occurs. EXAMPLES
Mark the Xorg server as protected: pgrep Xorg | xargs protect -p Protect all ssh sessions and their child processes: pgrep sshd | xargs protect -dip Remove protection from all current and future processes: protect -cdi -p 1 SEE ALSO
procctl(2) BUGS
If you protect a runaway process that allocates all memory the system will deadlock. BSD
September 19, 2013 BSD
All times are GMT -4. The time now is 10:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy