Re: [Apiman-user] APIMAN Best Practice for Response Critical APIs

Hi Marc, - Measured the time it takes to do your custom auth calls? Just to quantify what the effect of the policy is. For example you could print out timestamps, and/or compare to a deployment with no custom policies set. [Manav] – There calls are very fast, we did test it, as there is a Redis backend. I tested it. - Tweaked JVM memory settings and/or GC? [Manav] – Well said, we tried it to find the best setting. - Increased the thread-pool sizes? [Manav] – Well said, we tried it to find the best setting. One straight question, can Elastic Search be a bottleneck? Will there be difference if we use RDS instead of Elastic Search? How heavy metrics calls to ES? Thanks, Manav From: Marc Savy [mailto:marc.savy@redhat.com] Sent: 06 February 2017 18:34 To: Manvendra Rai Cc: apiman-user(a)lists.jboss.org Subject: Re: [Apiman-user] APIMAN Best Practice for Response Critical APIs Just to kick off the conversation: Have you: - Measured the time it takes to do your custom auth calls? Just to quantify what the effect of the policy is. For example you could print out timestamps, and/or compare to a deployment with no custom policies set. - Tweaked JVM memory settings and/or GC? - Increased the thread-pool sizes? On 6 February 2017 at 12:24, <Manvendra.Rai@ril.com<mailto:Manvendra.Rai@ril.com>> wrote: Hello All, We are using APIMAN for very response time critical APIs like - Upload API for uploading picture, videos etc.. to AWS S3. We don't want to upload files directly to S3 as there are few custom authentication & auth(via Redis In-Memory DB/Cache) checks we perform via our custom plugins in APIMAN. While, our APIs run OK without APIMAN, we see response time degrading considerably with APIMAN. What could be some of the best practices we should follow for performance tuning? We tried WildFly & Tomcat, though latter comparatively performed better, overall response time didn’t improve much. Thanks, Manav "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential and may be privileged. If you are not the intended recipient, you are hereby notified that any review, re-transmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment." _______________________________________________ Apiman-user mailing list Apiman-user@lists.jboss.org<mailto:Apiman-user@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/apiman-user "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email. and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."