01-20-2014
What processes are eating up CPU?
How much net traffic is there? Are packets being dropped or retried?
You have one active task and 217 sleeping tasks? What are they waiting for?
Do you have zombies filling up your process table?
If this is a Big data server, how do the disk queues look? Are you getting I/O errors?
Is anything else going on every 3-4 days? Does it happen at the same time-of-day? Do you immediately reboot when it starts to get slow? Once it starts getting slow, does it stay consistently slow? Does it get increasingly slower?
Are other VMs on this machine seeing any increased activity or slower response times too?
9 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
The site has gone slow for quite some time...
Can you do somethin abt it (2 Replies)
Discussion started by: DPAI
2 Replies
2. SCO
Hi All
We have one SCO Server here and it never gives us any trouble. Until Now!! Well its not earth shattering but we have one user who is complaining of a very slow response time when changing to his Home Directory. Other users who have similar profiles are OK. I have su'd to this user and I can... (0 Replies)
Discussion started by: JohnOB
0 Replies
3. Shell Programming and Scripting
Hi,
I would like to list latest 2 days, 3 days or 4 days,etc of files in the directory...
how? is it using ls? (3 Replies)
Discussion started by: happyv
3 Replies
4. Solaris
I'm facing a problem when trying to ssh to SUN servers with solaris OS,it takes a long time until prompted for password ..after connecting to the server everything work fine..how can I solve this issue??? (11 Replies)
Discussion started by: mm00123
11 Replies
5. SCO
The syslog shows:
FEB 5 17:42:07 NGXXXXX SYSLOG: SCOADM: LOCALHOST {SCO_NETWORKSPOOLER} {LPD} ERR
OR SCO_OFACE_MSG_ERROR {ERROR {{SCO_OSA_ERR_PROCESSING_FAILURE {GENERAL FAILURE
OCCURED IN PROCESSING THE REQUEST.}} {SCO_PRINTER_OSA_ERR_RLP_NOT_INSTALLED {THE
TCP/IP RLP REMOTE PRINTING PACKAGE... (2 Replies)
Discussion started by: gagan8877
2 Replies
6. Shell Programming and Scripting
i need a script that can tell me the date 2 days ago or 3 days ago.
please help (7 Replies)
Discussion started by: tomjones
7 Replies
7. Shell Programming and Scripting
Hi.. i have written a shell script and made this script to run on every day night 11: 55 pm using a cron job.
This cron job running for some days and is not running for some day. but i need this script to run every day night. Please help me.
Here is the cron tab entries,
55 23 * * *... (1 Reply)
Discussion started by: vidhyaS
1 Replies
8. Shell Programming and Scripting
Hi guys i need advice on the approach to this one......
I have a file say called
Thisfile.20130524.txt
i need to work out from the date 20130524 what day of the week that was and then process the file in 3 working days. (so not counting saturday or sunday....(will not worry about bank... (2 Replies)
Discussion started by: twinion
2 Replies
9. UNIX for Beginners Questions & Answers
How to find a file that's modified more than 2 days ago but was modified less than 5 days ago by use of any Linux utility ? (4 Replies)
Discussion started by: abdulbadii
4 Replies
LEARN ABOUT OPENSOLARIS
tc-bfifo
PBFIFO(8) Linux PBFIFO(8)
NAME
pfifo - Packet limited First In, First Out queue
bfifo - Byte limited First In, First Out queue
SYNOPSIS
tc qdisc ... add pfifo [ limit packets ]
tc qdisc ... add bfifo [ limit bytes ]
DESCRIPTION
The pfifo and bfifo qdiscs are unadorned First In, First Out queues. They are the simplest queues possible and therefore have no overhead.
pfifo constrains the queue size as measured in packets. bfifo does so as measured in bytes.
Like all non-default qdiscs, they maintain statistics. This might be a reason to prefer pfifo or bfifo over the default.
ALGORITHM
A list of packets is maintained, when a packet is enqueued it gets inserted at the tail of a list. When a packet needs to be sent out to
the network, it is taken from the head of the list.
If the list is too long, no further packets are allowed on. This is called 'tail drop'.
PARAMETERS
limit Maximum queue size. Specified in bytes for bfifo, in packets for pfifo. For pfifo, defaults to the interface txqueuelen, as speci-
fied with ifconfig(8) or ip(8). The range for this parameter is [0, UINT32_MAX].
For bfifo, it defaults to the txqueuelen multiplied by the interface MTU. The range for this parameter is [0, UINT32_MAX] bytes.
Note: The link layer header was considered when counting packets length.
OUTPUT
The output of tc -s qdisc ls contains the limit, either in packets or in bytes, and the number of bytes and packets actually sent. An
unsent and dropped packet only appears between braces and is not counted as 'Sent'.
In this example, the queue length is 100 packets, 45894 bytes were sent over 681 packets. No packets were dropped, and as the pfifo queue
does not slow down packets, there were also no overlimits:
# tc -s qdisc ls dev eth0
qdisc pfifo 8001: dev eth0 limit 100p
Sent 45894 bytes 681 pkts (dropped 0, overlimits 0)
If a backlog occurs, this is displayed as well.
SEE ALSO
tc(8)
AUTHORS
Alexey N. Kuznetsov, <kuznet@ms2.inr.ac.ru>
This manpage maintained by bert hubert <ahu@ds9a.nl>
iproute2 10 January 2002 PBFIFO(8)