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 /\/\ /\ >< `/ - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
