Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.



Read-Only Read-Only Topic
Go
Search
Notify
Tools
Report/Data cache
 Login/Join
 
Silver Member
posted
I'm trying to do some performance testing using a webfocus procedure. The problem I'm having is that when I run this fex for the first time it takes a certain amount of time, then when I run it again it runs much faster. The only way I can get it back to the original performance is to completely reboot my machine. I have all webfocus components installed on my machine. Do you know how I can reset things so I can get back to the original performance? I have EXPIRE_REPORTS set to 1, I've cleared the browser cache, I've stopped and restarted the http server and the Webfocus report server and nothing seems to reset things. The only way I can get back to the original performance is to reboot the computer.

Thanks,
Ron
 
Posts: 38 | Location: Milwaukee | Registered: April 28, 2005Report This Post
Gold member
posted Hide Post
Against what database are you running the report against. i.e is it FOCUS , Oracle


Webfocus 7.6.2 on Windows Enterprise 2003 Server and
Webfocus 7.6.2 on HP Unix Server
 
Posts: 74 | Location: London | Registered: January 28, 2005Report This Post
Silver Member
posted Hide Post
The report is being run against a focus database.
 
Posts: 38 | Location: Milwaukee | Registered: April 28, 2005Report This Post
Expert
posted Hide Post
Have you tried adding a random variable to the focexec call, thus making it unique each time you make the call. There seems to be a bug in IE cache management, and clearing the cache is not enough.

Can't explain why the EXPIRE_REPORTS setting doesn't work, though.


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
<JG>
posted
Ron,

What version of WF are you running?
Do you have access to the WF ADMin console.

There is a facilty within the 5.x console to run a stress test.

This is server based and so client caching is not an issue.

The old fashioned method is to use EDASTART -x or EDASTART -t and take timings from that. However that requires mulitle users to submit at the same time.

The console stress testing manages that for you.

5.x is basic 7.x is much better and gives better stats.

JG
 
Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders