[prev in list] [next in list] [prev in thread] [next in thread]
List: esb-java-dev
Subject: [Dev] Remove unused subscription throttle policies when creating Micro gw project
From: Rajith Roshan <rajithr () wso2 ! com>
Date: 2019-03-14 8:53:34
Message-ID: CAL=cp-dsOYSK9Wo5OgdPAhAMuja3acmOFpwomXY_GxAj-1mB8Q () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi all,
Currently in microgateway(MGW) when we create the project directory we
fetch all the subscription and application policies and we generate the
source for each policy. In each policy there is ever running loop
(forever), in back ground to update the throttle counters. But the issue
some of the subscription policies(tiers) might not be used in any of the
APIS in MGW and these not used policies running in the background might be
consuming some CPU cycles
So we thought of filter out the subscription policies(tiers) which are
attached to any of the APIs exposed via MGW.
For ex if API Foo is attach with policy 100PerMin and API Bar is attached
with policies 75PerMin and 50PerMin , then if we are only exposing API
"Foo" and "Bar" from MGW we will only create source files for those
subscription policies only, even though there are many subscription
policies defined in the admin portal of APIM.
Do you find any issues with this approach
--
*Rajith Roshan* | Associate Technical Lead | WSO2 Inc.
(m) +94-717-064-214 | (e) rajithr@wso2.com <shenavi@wso2.com>
<https://wso2.com/signature>
[Attachment #5 (text/html)]
<div dir="ltr">Hi all,<div>Currently in microgateway(MGW) when we create the project \
directory we fetch all the subscription and application policies and we generate the \
source for each policy. In each policy there is ever running loop (forever), in back \
ground to update the throttle counters. But the issue some of the subscription \
policies(tiers) might not be used in any of the APIS in MGW and these not used \
policies running in the background might be consuming some CPU cycles \
</div><div><br></div><div>So we thought of filter out the subscription \
policies(tiers) which are attached to any of the APIs exposed via MGW. \
</div><div>For ex if API Foo is attach with policy 100PerMin and API Bar is attached \
with policies 75PerMin and 50PerMin , then if we are only exposing API \
"Foo" and "Bar" from MGW we will only create source files for \
those subscription policies only, even though there are many subscription policies \
defined in the admin portal of APIM.</div><div>Do you find any issues with this \
approach<br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" \
data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div \
dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b>Rajith Roshan</b> | \
Associate Technical Lead | <span style="font-size:12.8px">WSO2 Inc.</span><div><span \
style="font-size:12.8px">(m) +94-717-064-214 | (e) <a \
href="mailto:shenavi@wso2.com" style="color:rgb(17,85,204)" \
target="_blank">rajithr@wso2.com</a></span><span \
style="font-size:12.8px"><br></span></div><div><span \
style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px"><a \
href="https://wso2.com/signature" style="color:rgb(17,85,204)" target="_blank"><img \
src="http://c.content.wso2.com/signatures/wso2-mail-signature-general.png" \
width="200" height="35"></a></span></div></div></div></div></div></div></div></div></div></div></div></div></div>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic