mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeff Busch" <jbusch@half.com>
To: "David Lang" <dlang@diginsite.com>
Cc: <linux-kernel@vger.kernel.org>, <roswell-list@redhat.com>
Subject: RE: [problem] RH 2.4.7-2 kernel slows to a crawl under heavy i/o
Date: Wed, 22 Aug 2001 22:39:06 -0500	[thread overview]
Message-ID: <NEBBJGKHGENBAPAMDILGGEHJGOAA.jbusch@half.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108221633280.3868-100000@dlang.diginsite.com>


> I have been trying to duplicate a similar problem in my lab that happened
> to me on a production box with 2.4.5. do you have a test that will allow
> you to replicate the problem at will?

ok here's a reply from our developer:

--------------------

probably the best way to reproduce the environment would be to write a
C++ class that has a method on it that goes and maps a file, touches
all the memory in that file, and then returns.  add another method
that takes a number and returns that same number.  then run that code
through swig and write a mod_perl interface to call the first method
then call the second method in a loop (10 times should be good), then
storable::freeze an array of results and print it to stdout.

this ought to emulate the kinds of things we do there.  you might
actually have that method take a number and return a string (literal)
instead of a number, just to exercise swig a little more.

--------------------

Note that the file must be large; maybe 50% greater than physical RAM.

Jeff

  parent reply	other threads:[~2001-08-23  3:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22 21:57 Jeff Busch
2001-08-22 22:12 ` Alan Cox
2001-08-23 10:26   ` Francois Romieu
2001-08-22 23:35 ` David Lang
2001-08-23  1:10   ` Jeff Busch
2001-08-23  3:39   ` Jeff Busch [this message]
2001-08-23  3:31 ` Daniel Phillips

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=NEBBJGKHGENBAPAMDILGGEHJGOAA.jbusch@half.com \
    --to=jbusch@half.com \
    --cc=dlang@diginsite.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roswell-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®