This discussion is archived
3 Replies Latest reply: Aug 17, 2010 12:21 PM by kk - oracle RSS

SLA Rate configuration in OCSG

779544 Newbie
Currently Being Moderated
Hi,

OCSG provides Traffic control for its communication services using SLA Rate and quota. In SLA we can set transaction rate Tx/msec for perticular method (ex. SendSMS etc.) or for entire service. Suppose we set transaction rate as 5/60000 (ie 5 tx/minute) then it should not allow more than 5 transaction in one minute. If you set higher rate in your duration test for incoming message you will find that it will give you few Policy denied exception and then passes few message and again gives few exception and so on. I mean it allows more than 5 tx in one minute. Accoridng to Oracle, it is sue to Budget sercvice and it is configurred accoring to this logic. Can anyone please explain this in more clarity. If any case we allow more than 5 Tx/Minute. How we can promise to operators that SPs will not use transaction rates defined more than defined in SLA. It should not allow more than defined in the SLA. In earlier verions of WLNG (OCSG) it was working fine.
  • 1. Re: SLA Rate configuration in OCSG
    kk - oracle Explorer
    Currently Being Moderated
    If an SLA is defined to be 5 TX/minute and OCSG is allowing more than 5 tx/minute consistently (for eg., You ran duration test for a minute and OCSG allowed more than 5 requests) then it's a product bug. Please file a bug with support, but I highly doubt that this is broken.
  • 2. Re: SLA Rate configuration in OCSG
    779544 Newbie
    Currently Being Moderated
    Hi,

    I have already done that. According to product team it is designed in this way only. Budget service may allow intially more number of transaction but average number will be apprx equal to rate defined in SLA. Budget service section in OCSG documentation describes this. But bit complicated to understand and alomost impossible to achive exact SLA rate.
  • 3. Re: SLA Rate configuration in OCSG
    kk - oracle Explorer
    Currently Being Moderated
    This is how the budget service/SLA enforcement works:
    If you define an SLA with rate control as x sms/y sec. From the time first request is sent, budget starts to diminish. At this point budget will be x-1. Say you've sent another request after n seconds, then it would be (x-2) + x*(y/n) or x whichever is higher. This x*(y/n) is added to the budget, because during those n seconds.
    Since it is hard to define an interval in absolute time, budget service is designed this way to properly control the flow.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points