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

[Manvendra.Rai at ril.com]

Right, we have this testing going right away here.

From: Marc Savy [mailto:marc.savy at redhat.com]
Sent: 06 February 2017 19:52
To: Manvendra Rai
Cc: apiman-user at lists.jboss.org
Subject: Re: [Apiman-user] APIMAN Best Practice for Response Critical APIs

Also, as a suggestion coming from another conversation between Eric and Ram, you might want to check performance with metrics disabled - the current ESMetrics implementation may not be coping under high load.

apiman-gateway.metrics=io.apiman.gateway.engine.impl.InMemoryMetrics
apiman-manager-ui.metrics.enable=false

We'll look at optimising it; shouldn't be difficult.



On 6 February 2017 at 13:04, Marc Savy <marc.savy at redhat.com<mailto:marc.savy at redhat.com>> wrote:
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 at ril.com<mailto:Manvendra.Rai at 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 at lists.jboss.org<mailto:Apiman-user at 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."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/apiman-user/attachments/20170206/a8af69f7/attachment.html