I'm looking for a script or some other application that will use up a lot of memory on a Solaris or Linux server, in order to test a monitoring application. So far I have found a script that's good for CPU usage but it does nothing for memory. I have also tried the application called 'stress' (found here) but either it isn't using up enough memory to hit the monitoring threshold, or I'm not using it right, or it's just not suited to this kind of test.
So far the only method I have found is just lowering the threshold enough for an alarm to get sent, but that kinda seems like cheating n_n
Hi there.
First things first, this is nothing to do with the internet or ISP speed, I know what that is, I know what it's doing.
I have a cluster of 128 single board computers running a branch of Debian. I want to run some kind of stress test to ensure they can transfer data (a) to each... (2 Replies)
I was hoping to test a bug posted by oracle, which indicates that the system may crash when using a zfs volume as a swap device. We moved swap away from zfs and over to raw disk devices in order to stop the crashes we've been experiencing.
What I wanted to do was to re-create the crash in a... (8 Replies)
Hi,
I am a newbee in the solaris administration. My question is how to
1. Check the total CPU and memory of a global zone.
2. Check the allocated CPU and memory for each of the residing non-global zones.
I have already tried prtconf which gives the following output
/usr/sbin/prtconf... (4 Replies)
I need to find out if the NIC on my MP-RAS box is bad. Unfortunately just sending out a ping to the loop back is not going to cut it. I need to be able to send out packets of information for several minutes at a time. I can't seem to find a tool or command to do this. Is anyone aware of a way to... (1 Reply)
18:45:47 # free -m
total used free shared buffers cached
Mem: 96679 95909 770 0 1530 19550
-/+ buffers/cache: 74828 21851
Swap: 12287 652 11635
Hi all. The below output is from a RHEL 4.5... (0 Replies)
Hi,
Your great help is very appreciated. I am looking for any Unix command or tool for doing Stress/Load test of php files at command prompt.
I tried torture.pl but it is not working after20 concurrent threads/users.
as it is very urgent for me..please suggest ur ideas asap.
thanks (5 Replies)
Hi to all,
Recently i am testing an equipment that runs in i586 fedora linux. I have to test mmap function. For that i determined to fill the memory and run the required application to check whether it throws any mmap error regarding low resources.
This is the line that does the allocation. ... (3 Replies)
Anyone know of the best tools for the job, I've used
vmstat, prtdiag and dmesg but want somehting to really interogate the memory and report.
Any ideas ? its on a SUN e6500
:D thanks (2 Replies)
memtester(8) Maintenance Commands memtester(8)NAME
memtester - stress test to find memory subsystem faults.
SYNOPSIS
memtester [-p PHYSADDR] <MEMORY> [ITERATIONS]
DESCRIPTION
memtester is an effective userspace tester for stress-testing the memory subsystem. It is very effective at finding intermittent and non-
deterministic faults. Note that problems in other hardware areas (overheating CPU, out-of-specification power supply, etc.) can cause
intermittent memory faults, so it is still up to you to determine where the fault lies through normal hardware diagnostic procedures;
memtester just helps you determine whether a problem exists.
memtester will malloc(3) the amount of memory specified, if possible. If this fails, it will decrease the amount of memory requested until
it succeeds. It will then attempt to mlock(3) this memory; if it cannot do so, testing will be slower and much less effective. Run
memtester as root so that it can mlock the memory it tests.
Note that the maximum amount of memory that memtester can test will be less than the total amount of memory installed in the system; the
operating system, libraries, and other system limits take some of the available memory. memtester is also limited to the amount of memory
available to a single process; for example, on 32-bit machines with more than 4GB of memory, memtester is still limited to less than 4GB.
Note that it is up to you to know how much memory you can safely allocate for testing. If you attempt to allocate more memory than is
available, memtester should figure that out, reduce the amount slightly, and try again. However, this can lead to memtester successfully
allocating and mlocking essentially all free memory on the system -- if other programs are running, this can lead to excessive swapping and
slowing the system down to the point that it is difficult to use. If the system allows allocation of more memory than is actually avail-
able (overcommit), it may lead to a deadlock, where the system halts. If the system has an out-of-memory process killer (like Linux),
memtester or another process may be killed by the OOM killer.
So choose wisely.
OPTIONS -p PHYSADDR
tells memtester to test a specific region of memory starting at physical address PHYSADDR (given in hex), by mmap(2)ing /dev/mem.
This is mostly of use to hardware developers, for testing memory-mapped I/O devices and similar. Note that the memory region will
be overwritten during testing, so it is not safe to specify memory which is allocated for the system or for other applications;
doing so will cause them to crash. If you absolutely must test a particular region of actual physical memory, arrange to have that
memory allocated by your test software, and hold it in this allocated state, then run memtester on it with this option.
MEMORY the amount of memory to allocate and test, in megabytes by default. You can include a suffix of B, K, M, or G to indicate bytes,
kilobytes, megabytes, or gigabytes respectively.
ITERATIONS
(optional) number of loops to iterate through. Default is infinite.
NOTE
memtester must be run with root privileges to mlock(3) its pages. Testing memory without locking the pages in place is mostly pointless
and slow.
EXIT CODE
memtester's exit code is 0 when everything works properly. Otherwise, it is the logical OR of the following values:
x01 error allocating or locking memory, or invocation error
x02 error during stuck address test
x04 error during one of the other tests
AUTHOR
Written by Charles Cazabon.
REPORTING BUGS
Report bugs to <charlesc-memtester-bugs@pyropus.ca>.
COPYRIGHT
Copyright (C) 2009 Charles Cazabon
This is free software; see the file COPYING for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
memtester 4 July 2009 memtester(8)
