• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

RES: OneWorld - Multithreading


VIP Member

UBEs are very database intensive. And that means disk-intensive. The UBE
process is probably most of the time waiting for the database to deliver the
requested data and releases the CPU until that is done. And SQL-server is
waiting for the disk to return the requested blocks from the harddrive
It's natural that such a process takes a small percentage of your CPU, even
on an otherwise idle machine, and that's not only on NT.


-----Mensagem original-----
De: owner-jdelistml@jdelist.com [mailto:eek:wner-jdelistml@jdelist.com]Em
nome de jgersic
Enviada em: quinta-feira, 30 de agosto de 2001 16:11
Para: jdelistml@jdelist.com
Assunto: RE: OneWorld - Multithreading

Thanks for the replies, I think my understanding is pretty clear now
of JDE's definition of 'multithreaded'. One other question, and this may
how my naivety of NT..but when a UBE is processing, why does the
runbatch.exe only take a few percent of the available cpu resources? I
have put the priority to 'high' through the task manager, but runbatch
still only take a few percent. If there was a way to ensure that the
runbatch program would take full advantage of a cpu it would decrease
processing time dramatically. Now that I am playing with the logic
server I can see that the run batch job is muddeling about at maybe 20%
of a cpu, and SQL is taking 3-20% on the database server. Is there any
other tuning I can perform, or am missing? Lastly, has anyone migrated
from SQL7--> SQL2k and seen a performance boost?


Xe - SP16/Update2, NT/SP6a, SQL7/SP3, WTS/Metaframe 1.8

Xe, Update2, SP16
NT/SP6a, SQL7/SP3, WTS/Metaframe 1.8