Does stress testing rule out bad RAM/CPU

[Kohlmann]

Hi all,
Recently, I am testing equipment that works in Fedora Linux i586. I had to test the function mmap. For this, I decided to fill the memory and run the application needed to see if it throws any error mmap resource low.
This is the line that distribution.
p \ u003d (long double *) malloc (BUFFSIZE);
In Windows Explorer process, I noticed that the value than ever, we give BUFFSIZE it will increase the size of "Private Bytes" but have not worked together in memory or real memory. Under Linux, the memory remains the same even after allocating approximately 1000MB. Thus, the system remains stable. The memset "package is not available and can be installed, there is also no memory swap. The equipment operates in its own video memory which is about 500MB. I want a C program to fill memory and crash the system. Kindly help. Also I want to know that does stress testing rule out bad RAM/CPU.

[Alchmey]

Linux shows the memory that is malloced but never used in any way under its' virtual memory stats. If you want the system to operate effectively from memory, and not killing random processes to resume, you want to turn to May and overcommit OOM-kill on your Linux system. With that activated, it can not allocate memory that you actually use. I can not predict the effects of this phenomenon on a system totally lacking in the swap memory though - why your system does not have it? Windows has been tested under these conditions too? Also I don't think that stress testing rule affects the RAM or CPU badly.

[Kane01]

You can try the following coding :

 echo 2> / proc / sys / vm / overcommit_memory
 echo 0> / proc / sys / vm / oom-kill

Let me tell you that these settings are not persistent. If you restart the machine, they will be back to default values. Who are frankly more stable for the reasons you have discovered - this makes it more difficult for memory leaks endless killing your machine. Not all versions of Linux have / proc / sys / vm / oom-kill, I'm hunting for an alternative. You find it listed in May by sysctl-A.

[Arley]

You have also said that The memset "package is not available and can be installed, there is also no memory swap." I would like to discuss on this. Memset which package.?? If you mean the C function, it has certainly memset. You must include string.h. Including the string.h will definitely resolve your issue.

[Golfert]

I am sure that the swap is not available. The manufacturer installs in this way :

<stdio.h>
  Stdlib.h
  <string.h>

  int main (int argc, char * argv [])
  (
          void * myblock = NULL;
          int count = 0;
          char ch, * mem;

          if (argv [1] == NULL) (
                  printf ("usage: blast <memmory space> \ n");
                  exit (0);
          )

          memReq int = 0;
          memReq = strtol (argv [1], & mem, 10);

          while (count <memReq)
          (
                  myblock = (void *) malloc (megabytes);
                  if (! myblock) break;
                  memset (myblock, 1 megabyte);
                  printf ("Allocating% d Currently MB \ n", + + count);
          )

          do (
                  printf ("Hit 'y' to exit ... \ n");
                  scanf ("% c", & ch);
          ) While (ch == 'y');

          free (myblock);
          exit (0);
  )

[Sebastian.j]

I downloaded the Gimp (version 2.6.8) compressed, I unpacked and in the INSTALL file I found the following steps :

% Tar xvfz gimp-2.6.x.tar.gz # unpack the sources
% Cd gimp-2.6.x # change to the toplevel directory
%. / Configure # run the `configure 'script
% Make # build GIMP
% Make install # install GIMP

First and second steps are made (obvious), and applying the third (configuration), it begins to give an error. How to solve this.?? Please help I am not good in stress testing.!!

[MattyBoy]

To determine the optimal values for analysis of the server, or reference, he must first test the configuration of a pilot system in a controlled environment. Then you must perform the test in a simulated production environment to determine how the configuration of the production environment affects the results of the pilot scheme. When planning phase stress testing of your development cycle, you get interested in the following points :

• Hardware and Software
• Server Configuration
• Security Configuration
• Configuring the user load
• Selecting the right tools stress