We need to speed up the performance of our .fex programs. We run WebFocus Maintain programs for inquiry and maintance. The Maintain programs submit .fex programs to create reports that get Emailed to customers durning the day. The .fex programs take a minute or two to run which the users complain about.
1. We currently license two cores from IBI on our server. What effect would a license for more cores have on performance?
2. Would more RAM in our users PCs speed up .fexes?
3. Would more RAM in the server speed them up?

Thanks, Kent

This message has been edited. Last edited by: <Kathryn Henning>,

quote:

a minute or two

- soooo long?

Are you reading DBMS tables? Have you turned SQL traces on, to ensure the optimum SQL is generated by the WF data adapter?

Kent,

I agree with Francis. Use traces to identify whether your sql is efficient or not. I created this fex that I point to on the Data Server and include into any fex that I need to investigate for efficiency.

 
-*******************************************************************************
-* Fex Name:     = SQL Translation
-* Technical Name: = GLB9997F00.FEX
-* Description:  = This fex is for understanding the SQl being passed to the Database
-*				   including this fex in your query will stop WebFOCUS from sending a
-*				   query to the database and show you what was generated.
-* Parameters:   = none
-*******************************************************************************
-*               Update Log
-*******************************************************************************
-*    date     Initals     Reason for Change
-*  --------   -------     -----------------------------------------------------
-*  4/9/2013    EJW        Initial creation
-*******************************************************************************
-*******************************************************************************
-* Utilize the check file command if there appears to be issues with the length of the
-* master file table
-*CHECK FILE MF_FILE_NAME
-*******************************************************************************
 SET TRACEOFF=ALL
 SET TRACEON=SQLAGGR//CLIENT
 SET TRACEON=STMTRACE//CLIENT
 SET TRACEON=STMTRACE/2/CLIENT
 SET TRACEUSER=ON
 SET TRACESTAMP=OFF
 SET XRETRIEVAL=OFF

 

Notice XRETRIVAL=OFF will turn off the return of records so all you get is the SQL. The first thing you need to do is understand where your time is being taken up.

Is the query efficient and translated properly to SQL?
Is the database request running quickly?
Are there a lot of records that need to be moved between the DB and the Reporting Server

Once you have identified what is causing the slow performance you can look at the appropriate actions.

Do you need to create aggregate tables?
Do you need to increase the data transfer speed between the DB and reporting Server?
Does your reporting server need to perform quicker?
Do you need to re-write your focus code so that the adapter translates the request properly?
Can you utilize SQL pass thru to more efficiently grab your data and minimize the records being passed back and forth?

I hope this helps in your search for answers.