public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Maximiliano Curia <maxy@rivero.com.ar>
To: "Mgr. Peter Tuharsky" <tuharsky@misbb.sk>,
	linux mailing list <linux-msdos@vger.kernel.org>
Subject: Re: Dosemu and clipper applications eating all CPU
Date: Wed, 28 Apr 2004 16:52:36 -0300	[thread overview]
Message-ID: <1083181954.2220.351.camel@peperina> (raw)
In-Reply-To: <408F4752.4060508@misbb.sk>

On Wed, 2004-04-28 at 02:55, Mgr. Peter Tuharsky wrote:
>     I have similar problem with Clipper app. In some menus, the CPU is 
> 100% consumed by a loop, an AthlonXP1900+ :o) Note the program ran on 
> 386 in past. There are two users working simultaneously (one thru thin 
> client) and sometimes the response is VERY slow; program even fails to 
> display entered letters in realtime.

I'm still trying to solve this problem, I've been testing some different
usleep times in different int calls, and the best I could achieve was
75% of CPU usage when idle, 1% when busy, with a very slow
responsiveness, but usable, up to 3 users.

Vanilla dosemu eats 98% CPU, 1-2% when idle, and has an excellent
responsiveness when there is only 1 user. And its still usable with 2
users, if there is a third it becomes unresponsive.

>     In other section I have strictly different problem. When some 
> database-intensive actions are taken, typically reindexing, the CPU is 
> used by some 1% and thus the operation runs VERY slow too. Computer is 
> bored and user too :o(

It's pretty annoying that when the application is doing something it
drops the cpu usage.

>     If somebody fixed these two issues (if I were programmer, I would), 
> I'd very like it. Or can somebody do it for some symbolical amount of 
> money? Although there could be a little difficulty paying from my country..

In my case, it's not about money. I have to fix this so my users don't
kill me. But you are encouraged to donate money to the dosemu project.

-- 
Saludos
/\/\ /\ >< `/

  reply	other threads:[~2004-04-28 19:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28  5:55 Dosemu and clipper applications eating all CPU Mgr. Peter Tuharsky
2004-04-28 19:52 ` Maximiliano Curia [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-28 17:32 Stas Sergeev
2004-03-15 19:17 Stas Sergeev
2004-03-15 17:50 Stas Sergeev
2004-03-15 18:07 ` Maurilio Longo
2004-03-12 22:33 Stas Sergeev
2004-03-15 11:53 ` Maurilio Longo
2004-03-11 18:44 Stas Sergeev
2004-03-10 19:36 Stas Sergeev
2004-03-10 22:55 ` Maurilio Longo
2004-03-11  8:29   ` Maurilio Longo
2004-03-10 18:36 Stas Sergeev
2004-03-09 20:16 Stas Sergeev
2004-03-10 15:29 ` Peter B. Steiger
2004-03-10 19:11 ` Maximiliano Curia
2004-03-08 16:11 Maximiliano Curia

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=1083181954.2220.351.camel@peperina \
    --to=maxy@rivero.com.ar \
    --cc=linux-msdos@vger.kernel.org \
    --cc=tuharsky@misbb.sk \
    /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