Sponsored Content
Full Discussion: how to stress the memory
Operating Systems Solaris how to stress the memory Post 302289507 by incredible on Thursday 19th of February 2009 09:00:45 PM
Old 02-19-2009
SUNVTS is a good tool to stress test a server. Usually before the system is thrown into production
 

9 More Discussions You Might Find Interesting

1. UNIX and Linux Applications

Solaris & Linux memory stress test?

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'... (0 Replies)
Discussion started by: Kraas
0 Replies

2. Programming

Stress testing memory using malloc in linux ??

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)
Discussion started by: frozensmilz
3 Replies

3. UNIX for Advanced & Expert Users

Stress Run

Please anyone can tell me what is Stress in unix and how can I Perform Stress Runs on the UNIX environment Please reply soon it's urgent:confused: (5 Replies)
Discussion started by: mubashir
5 Replies

4. Shell Programming and Scripting

Stress testing php files at Unix/Linux Command line

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)
Discussion started by: Malleswari
5 Replies

5. IP Networking

Stress Test a NIC

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)
Discussion started by: wardduncan
1 Replies

6. Solaris

[DOUBT] Memory high in idle process on Solaris 10 (Memory Utilization > 90%)

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

7. Solaris

Swap stress test

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)
Discussion started by: butchie3980
8 Replies

8. UNIX for Beginners Questions & Answers

Network stress test.

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)
Discussion started by: MuntyScrunt
2 Replies

9. UNIX for Beginners Questions & Answers

3rd party stress testing services

Hi all, bit of a forum newb here, so apologies if this has been covered else where, but I wonder if any of you has any experience with stress testing servers, specifically using 3rd party services. We run a very busy production system, and just haven't been able to simulate the user activity while... (1 Reply)
Discussion started by: dare99
1 Replies
OSMTEST(8)							 OpenIB Management							OSMTEST(8)

NAME
osmtest - InfiniBand subnet manager and administration (SM/SA) test program SYNOPSIS
osmtest [-f(low) <c|a|v|s|e|f|m|q|t>] [-w(ait) <trap_wait_time>] [-d(ebug) <number>] [-m(ax_lid) <LID in hex>] [-g(uid)[=]<GUID in hex>] [-p(ort)] [-i(nventory) <filename>] [-s(tress)] [-M(ulticast_Mode)] [-t(imeout) <milliseconds>] [-l | --log_file] [-v] [-vf <flags>] [-h(elp)] DESCRIPTION
osmtest is a test program to validate InfiniBand subnet manager and administration (SM/SA). Default is to run all flows with the exception of the QoS flow. osmtest provides a test suite for opensm. osmtest has the following capabilities and testing flows: It creates an inventory file of all available Nodes, Ports, and PathRecords, including all their fields. It verifies the existing inven- tory, with all the object fields, and matches it to a pre-saved one. A Multicast Compliancy test. An Event Forwarding test. A Service Record registration test. An RMPP stress test. A Small SA Queries stress test. It is recommended that after installing opensm, the user should run "osmtest -f c" to generate the inventory file, and immediately after- wards run "osmtest -f a" to test OpenSM. Another recommendation for osmtest usage is to create the inventory when the IB fabric is stable, and occasionally run "osmtest -v" to ver- ify that nothing has changed. OPTIONS
-f, --flow This option directs osmtest to run a specific flow: FLOW DESCRIPTION c = create an inventory file with all nodes, ports and paths a = run all validation tests (expecting an input inventory) v = only validate the given inventory file s = run service registration, deregistration, and lease test e = run event forwarding test f = flood the SA with queries according to the stress mode m = multicast flow q = QoS info: dump VLArb and SLtoVL tables t = run trap 64/65 flow (this flow requires running of external tool) (default is all flows except QoS) -w, --wait This option specifies the wait time for trap 64/65 in seconds It is used only when running -f t - the trap 64/65 flow (default to 10 sec) -d, --debug This option specifies a debug option. These options are not normally needed. The number following -d selects the debug option to enable as follows: OPT Description --- ----------------- -d0 - Ignore other SM nodes -d1 - Force single threaded dispatching -d2 - Force log flushing after each log message -d3 - Disable multicast support -m, --max_lid This option specifies the maximal LID number to be searched for during inventory file build (default to 100) -g, --guid This option specifies the local port GUID value with which OpenSM should bind. OpenSM may be bound to 1 port at a time. If GUID given is 0, OpenSM displays a list of possible port GUIDs and waits for user input. Without -g, OpenSM trys to use the default port. -p, --port This option displays a menu of possible local port GUID values with which osmtest could bind -i, --inventory This option specifies the name of the inventory file Normally, osmtest expects to find an inventory file, which osmtest uses to val- idate real-time information received from the SA during testing If -i is not specified, osmtest defaults to the file 'osmtest.dat' See -c option for related information -s, --stress This option runs the specified stress test instead of the normal test suite Stress test options are as follows: OPT Description --- ----------------- -s1 - Single-MAD response SA queries -s2 - Multi-MAD (RMPP) response SA queries -s3 - Multi-MAD (RMPP) Path Record SA queries Without -s, stress testing is not performed -M, --Multicast_Mode This option specify length of Multicast test: OPT Description --- ----------------- -M1 - Short Multicast Flow (default) - single mode -M2 - Short Multicast Flow - multiple mode -M3 - Long Multicast Flow - single mode -M4 - Long Multicast Flow - multiple mode Single mode - Osmtest is tested alone, with no other apps that interact with OpenSM MC Multiple mode - Could be run with other apps using MC with OpenSM. Without -M, default flow testing is performed -t, --timeout This option specifies the time in milliseconds used for transaction timeouts. Specifying -t 0 disables timeouts. Without -t, OpenSM defaults to a timeout value of 200 milliseconds. -l, --log_file This option defines the log to be the given file. By default the log goes to stdout. -v, --verbose This option increases the log verbosity level. The -v option may be specified multiple times to further increase the verbosity level. See the -vf option for more information about. log verbosity. -V This option sets the maximum verbosity level and forces log flushing. The -V is equivalent to '-vf 0xFF -d 2'. See the -vf option for more information about. log verbosity. -vf This option sets the log verbosity level. A flags field must follow the -D option. A bit set/clear in the flags enables/disables a specific log level as follows: BIT LOG LEVEL ENABLED ---- ----------------- 0x01 - ERROR (error messages) 0x02 - INFO (basic messages, low volume) 0x04 - VERBOSE (interesting stuff, moderate volume) 0x08 - DEBUG (diagnostic, high volume) 0x10 - FUNCS (function entry/exit, very high volume) 0x20 - FRAMES (dumps all SMP and GMP frames) 0x40 - ROUTING (dump FDB routing information) 0x80 - currently unused. Without -vf, osmtest defaults to ERROR + INFO (0x3) Specifying -vf 0 disables all messages Specifying -vf 0xFF enables all messages (see -V) High verbosity levels may require increasing the transaction timeout with the -t option -h, --help Display this usage info then exit. AUTHORS
Hal Rosenstock <hal@xsigo.com> Eitan Zahavi <eitan@mellanox.co.il> OpenIB August 11, 2008 OSMTEST(8)
All times are GMT -4. The time now is 02:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy