[Apiman-user] APIMAN configuration for high-load application

[Ram.Tanna at ril.com]

Hi Marc,

We haven't done any major changes in the default configuration and in property file.

Trying out Vert.x-based gateway would not be feasible at this moment as we are into the production phase, and we want to achieve best output from minimal modifications.

Regards,
Ram Tanna



From: Marc Savy <marc.savy at redhat.com<mailto:marc.savy at redhat.com>>
Date: Tuesday, 7 February 2017 at 6:39 PM
To: Ram <ram.tanna at ril.com<mailto:ram.tanna at ril.com>>
Cc: "apiman-user at lists.jboss.org<mailto:apiman-user at lists.jboss.org>" <apiman-user at lists.jboss.org<mailto:apiman-user at lists.jboss.org>>, Manvendra Rai <manvendra.rai at ril.com<mailto:manvendra.rai at ril.com>>, Anshul Agrawal <Anshul.Agrawal at ril.com<mailto:Anshul.Agrawal at ril.com>>, "ram_tanna3 at yahoo.in<mailto:ram_tanna3 at yahoo.in>" <ram_tanna3 at yahoo.in<mailto:ram_tanna3 at yahoo.in>>
Subject: Re: [Apiman-user] APIMAN configuration for high-load application

Hi,

Can you share a bit of information about your setup?

For instance, if you share apiman.properties with any sensitive information taken out.

This sounds like it could be a good candidate for trying our Vert.x-based gateway. I've been working a lot on it lately - it might be worth trying out in a test deployment. However, I'd need to know more about your existing setup, as the bottleneck might be elsewhere.

Regards,
Marc

On 7 February 2017 at 12:55, <Ram.Tanna at ril.com<mailto:Ram.Tanna at ril.com>> wrote:
Dear Team,

We are using APIMAN in our application which would have 40k concurrent requests.

There would be around 7000 requests/second. Out of which 2500 requests are for uploading and downloading a file with payload size of 512 KB/request. Other request will have payload of 50 to 80 KB.

Folks who are using apiman in their system, can please share your experience.

What would be the best configuration for such high-load application ?


Thanks and Regards,
Ram Tanna









"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/20170207/d5df461e/attachment.html