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

Hey Marc, Thank you for the contribution. I will make mentioned changes, and share the result with you. Regards, Ram Tanna From: Marc Savy <marc.savy@redhat.com<mailto:marc.savy@redhat.com>> Date: Wednesday, 15 February 2017 at 12:08 AM To: Ram <ram.tanna@ril.com<mailto:ram.tanna@ril.com>> Cc: "apiman-user@lists.jboss.org<mailto:apiman-user@lists.jboss.org>" <apiman-user@lists.jboss.org<mailto:apiman-user@lists.jboss.org>>, Manvendra Rai <manvendra.rai@ril.com<mailto:manvendra.rai@ril.com>>, "ram_tanna3@yahoo.in<mailto:ram_tanna3@yahoo.in>" <ram_tanna3@yahoo.in<mailto:ram_tanna3@yahoo.in>> Subject: Re: [Apiman-user] APIMAN configuration for high-load application Further to this, I've found that the threadpool between the gateway and the API can become exhausted. Bump it up using the following environment variable: -Dhttp.maxConnections=100 # Just an example, tweak as you see fit... JAVA_OPTS="-Xmx4g" ./bin/standalone.sh -Dhttp.maxConnections=100 On 14 February 2017 at 17:40, Marc Savy <marc.savy@redhat.com<mailto:marc.savy@redhat.com>> wrote: Another thought. In your WF10 standalone.xml you can try substantially boosting up the number of connections that Undertow allows: See: <request-limit name="limit-connections" max-concurrent-requests="15000" queue-size="100"/> An example is in the <filters> section of the following undertow config: https://github.com/wildfly/wildfly/blob/master/undertow/src/test/resource... On 9 February 2017 at 12:46, Marc Savy <marc.savy@redhat.com<mailto:marc.savy@redhat.com>> wrote: Any useful findings? On 7 February 2017 at 14:26, Marc Savy <marc.savy@redhat.com<mailto:marc.savy@redhat.com>> wrote: Hi, Check out Harry Trinta's contributions to this thread: https://lists.jboss.org/pipermail/apiman-user/2017-January/000758.html Have you done any profiling and observed any particular bottlenecks? Regards, Marc On 7 February 2017 at 14:09, <Ram.Tanna@ril.com<mailto:Ram.Tanna@ril.com>> wrote: 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@redhat.com<mailto:marc.savy@redhat.com>> Date: Tuesday, 7 February 2017 at 6:39 PM To: Ram <ram.tanna@ril.com<mailto:ram.tanna@ril.com>> Cc: "apiman-user@lists.jboss.org<mailto:apiman-user@lists.jboss.org>" <apiman-user@lists.jboss.org<mailto:apiman-user@lists.jboss.org>>, Manvendra Rai <manvendra.rai@ril.com<mailto:manvendra.rai@ril.com>>, Anshul Agrawal <Anshul.Agrawal@ril.com<mailto:Anshul.Agrawal@ril.com>>, "ram_tanna3@yahoo.in<mailto:ram_tanna3@yahoo.in>" <ram_tanna3@yahoo.in<mailto:ram_tanna3@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@ril.com<mailto:Ram.Tanna@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@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." "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."