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.
I am reviewing the following three (3) Configuration Settings (properties) of the DEFAULT Data Service, at our site: * cpu_limit (in seconds) * memory_limit (in KB) * disk_limit (in KB)
At the moment, all three are set to '-1' (unlimited - default value).
We are looking to guard against 'very bad' behaving requests, e.g., requests that go into an infinite Dialogue Manager loop.
Could anyone recommend or suggest values they have set, and found useful, for these three parameters?
I realize the amount of available CPU/space | type of request, would vary amongst environments/sites, I'm just looking for what community members have found reasonable/useful.
Thank you.This message has been edited. Last edited by: Kerry,
Pilot: WebFOCUS 8.2.06 Test: WebFOCUS 8.1.05M Prod: WebFOCUS 8.1.05M Server: Windows Server 2016/Tomcat Standalone Workstation: Windows 10/IE11+Edge Database: Oracle 12c, Netezza, & MS SQL Server 2019 Output: AHTML/XLSX/HTML/PDF/JSCHART Tools: WFDS, Repository Content, BI Portal Designer & ReportCaster
Could anyone recommend or suggest values they have set, and found useful, for these three parameters?
Wanted to add that I had opened a case with IB on this question. The HelpDesk suggested that a post to FocalPoint, would be the best way to get some suggestions.
As soon as you add a limit any job that falls into that limit will be affected.
Agreed. I will want to make sure that setting these three parms effect only 'very bad' behaving requests.
quote:
I would suggest first checking any current jobs to see what they are doing, then add some limits based on the observations.
Cool. I checked the 'CPU Time' and 'Memory Usage (KB)' values, from the WebConsole 'Data Service Agents page, for a typical request. I'll then multiply these values times some factor for the CPU/Memory settings. For the Disk setting I'll divide the total amount of free space on the drive by some factor.
Anyone else have any thoughts, or 'best practices, for these three settings?
You may also want to set limitations on users meaning how many agents a user can get. You don't want a user executing several long running requests tying up your server.