From: Frank Cox <theatre@sasktel.net>
To: Rodrigo Real <rreal@ucpel.tche.br>
Cc: linux-msdos@vger.kernel.org
Subject: Re: Cobol app takes 100% CPU
Date: Wed, 26 Mar 2008 09:28:13 -0600 [thread overview]
Message-ID: <20080326092813.df658a5e.theatre@sasktel.net> (raw)
In-Reply-To: <87bq51lk5j.fsf@pequena.ucpel.tche.br>
On Wed, 26 Mar 2008 09:55:20 -0300
Rodrigo Real <rreal@ucpel.tche.br> wrote:
> This cobol app always tried to eat the most of cpu it can, with 10 or
> 12 users the situation were acceptable, but now with 26 it is been
> very hard to work.
Have you tried Tame?
--
MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com
next prev parent reply other threads:[~2008-03-26 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 12:55 Cobol app takes 100% CPU Rodrigo Real
2008-03-26 15:28 ` Frank Cox [this message]
2008-03-27 12:11 ` Rodrigo Real
2008-03-27 14:20 ` Frank Cox
2008-03-27 15:57 ` Bart Oldeman
2008-03-27 17:53 ` Rodrigo Real
2008-03-27 17:53 ` Mike McCarty
2008-03-27 18:11 ` Rodrigo Real
2008-03-30 20:37 ` Jan Kandziora
2008-03-31 1:18 ` Rodrigo Real
-- strict thread matches above, loose matches on Subject: below --
2008-03-30 14:12 Manfred Scherer
2008-03-31 13:46 ` Rodrigo Real
2008-03-31 9:47 ` Manfred Scherer
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=20080326092813.df658a5e.theatre@sasktel.net \
--to=theatre@sasktel.net \
--cc=linux-msdos@vger.kernel.org \
--cc=rreal@ucpel.tche.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.