Sponsored Content
Operating Systems Solaris Rcap is increasing load average. Why ? Post 303029893 by TioTony on Saturday 2nd of February 2019 01:48:12 PM
Old 02-02-2019
This is a long shot from the offline storage in my brain, but I recall having a similar issue about 15 years ago and it was due to a memory DIMM failure. Maybe check for some hardware failures on the system.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

load average

we have an unix system which has load average normally about 20. but while i am running a particular unix batch which performs heavy operations on filesystem and database average load reduces to 15. how can we explain this situation? while running that batch idle cpu time is about %60-65... (0 Replies)
Discussion started by: gfhgfnhhn
0 Replies

2. UNIX for Dummies Questions & Answers

Load Average

Hello all, I have a question about load averages. I've read the man pages for the uptime and w command for two or three different flavors of Unix (Red Hat, Tru64, Solaris). All of them agree that in the output of the 2 aforementioned commands, you are given the load average for the box, but... (3 Replies)
Discussion started by: Heathe_Kyle
3 Replies

3. Shell Programming and Scripting

Determening load average.

Hi, I'm new to shell scripting. I need to make a script to add on to my cronjobs. The script must get the value of load average from my server and if its greater than 10 it should stop my apache service. I cant find a way to get the value of load average in integer type to do the check. Any... (4 Replies)
Discussion started by: jibsonline
4 Replies

4. UNIX for Dummies Questions & Answers

top - Load average

Hello, Here is the output of top command. My understanding here is, the load average 0.03 in last 1 min, 0.02 is in last 5 min, 0.00 is in last 15 min. By seeing this load average, When can we say that, the system load averge is too high? When can we say that, load average is medium/low??... (8 Replies)
Discussion started by: govindts
8 Replies

5. Solaris

load average query.

Hi, i have installed solaris 10 on t-5120 sparc enterprise. I am little surprised to see load average of 2 or around on this OS. when checked with ps command following process is using highest CPU. looks like it is running for long time and does not want to stop, but I do not know... (5 Replies)
Discussion started by: upengan78
5 Replies

6. UNIX for Dummies Questions & Answers

Please Help me in my load average

Hello AlL,.. I want from experts to help me as my load average is increased and i dont know where is the problem !! this is my top result : root@a4s # top top - 11:30:38 up 40 min, 1 user, load average: 3.06, 2.49, 4.66 Mem: 8168788k total, 2889596k used, 5279192k free, 47792k... (3 Replies)
Discussion started by: black-code
3 Replies

7. UNIX for Dummies Questions & Answers

Load Average threshold

What should be the threshold for load average of a quad core processor? What constitutes "good" and "bad" load average values? (2 Replies)
Discussion started by: proactiveaditya
2 Replies

8. Solaris

Load Average and Lwps

NPROC USERNAME SWAP RSS MEMORY TIME CPU 320 oracle 23G 22G 69% 582:55:11 85% 47 root 148M 101M 0.3% 99:29:40 0.3% 53 rafmsdb 38M 60M 0.2% 0:46:17 0.1% 1 smmsp 1296K 5440K 0.0% 0:00:08 0.0% 7 daemon ... (2 Replies)
Discussion started by: snjksh
2 Replies

9. UNIX for Dummies Questions & Answers

Help with load average?

how load average is calculated and what exactly is it difference between cpu% and load average (9 Replies)
Discussion started by: robo
9 Replies

10. HP-UX

Load average unit

Hi, On load average graph, unit is 100m, 200m, 300...800m. I don't understand what it means. Thx for helping (3 Replies)
Discussion started by: Michenux
3 Replies
Test::LectroTest::FailureRecorder(3pm)			User Contributed Perl Documentation		    Test::LectroTest::FailureRecorder(3pm)

NAME
Test::LectroTest::FailureRecorder - Records/plays failures for regression testing SYNOPSIS
use Test::LectroTest::Recorder; my $recorder = Test::LectroTest::Recorder->new("storage_file.txt"); my $recorder->record_failure_for_property( "property name", $input_hashref_from_counterexample ); my $failures = $recorder->get_failures_for_property("property name"); for my $input_hashref (@$failures) { # do something with hashref } DESCRIPTION
This module provides a simple means of recording property-check failures so they can be reused as regression tests. You do not need to use this module yourself because the higher-level LectroTest modules will use it for you when needed. (These docs are mainly for LectroTest developers.) The basic idea is to record a failure as a pair of the form [ <property_name>, <input hash from counterexample> ] and Dump these pairs into a text file, each record terminated by blank line so that the file can be read using paragraph-slurp mode. The module provides methods to add such pairs to a recorder file and to retrieve the recorded failures by property name. It uses a cache to avoid repetitive reads. METHODS
new(storage-file) my $recorder = Test::LectroTest::Recorder->new("/path/to/storage.txt"); Creates a new recorder object and tells it to use storage-file for the reading and writing of failures. The recorder will not access the storage file until you attempt to get or record a failure. Thus it is OK to specify a storage file that does not yet exist, provided you record failures to it before you attempt to get failures from it. get_failures_for_property(propname) my $failures = $recorder->get_failures_for_property("property name"); for my $input_hashref (@$failures) { # do something with hashref while (my ($var, $value) = each %$input_hashref) { # ... } } Returns a reference to an array that contains the recorded failures for the property with the name propname. In the event no such failures exist, the array will be empty. Each failure is represented by a hash containing the inputs that caused the failure. If the recorder's storage file does not exist or cannot be opened for reading, this method dies. Thus, you should call it from within an "eval" block. record_failure_for_property(propname, input-hashref) my $recorder->record_failure_for_property( "property name", $input_hashref_from_counterexample ); Adds a failure record for the property named propname. The record captures the counterexample represented by the input-hashref. The record is immediately appended to the recorder's storage file. Returns 1 upon success; dies otherwise. If the recorder's storage file cannot be opened for writing, this method dies. Thus, you should call it from within an "eval" block. SEE ALSO
Test::LectroTest::TestRunner explains the internal testing apparatus, which uses the failure recorders to record and play back failures for regression testing. LECTROTEST HOME
The LectroTest home is http://community.moertel.com/LectroTest. There you will find more documentation, presentations, mailing-list archives, a wiki, and other helpful LectroTest-related resources. It's also the best place to ask questions. AUTHOR
Tom Moertel (tom@moertel.com) COPYRIGHT and LICENSE Copyright (c) 2004-06 by Thomas G Moertel. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.12.3 2007-08-30 Test::LectroTest::FailureRecorder(3pm)
All times are GMT -4. The time now is 06:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy