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,

quote:

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.

This one is a difficult one to answer.

As soon as you add a limit any job that falls into that limit will be affected.

I would suggest first checking any current jobs to see what they are doing, then add some limits based on the observations.

Thank you Waz, for your thoughts.

quote:

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.

Yes we limit each user to 5 sessions or they would submit a bunch and go to lunch.

quote:

for a typical request

Would it be better to check one of the longer or more intensive fexes ?