× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MAPICS-L
  3. March 2002

RE: EFFECTS OF ODBC CALLS

Lloyd,

ODBC normally does show up but bad joins can definitely
impact 400 performace. Time slices of less than 2 min
in wrkactjob are not really valid since the 400 can
spike at any time. I would start wrkactjob, reset the
stats, put the cursor over the cpu% col and then hit
F16 to see from high to low. If you have not already
done that it might help. Most of the async system
jobs dealing with TCP/IP will show you the IP that
they are servicing. So if you isolate one you can
ping your network and look from there.

Also note that save restore operation can greatly slow
down a 400 and dont really evidence themselves in
wrkactjob either.

Konrad

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.