WSO2 ESB 5.0.0 - maximum traffic it can hold - wso2

I am trying to analyse what will be the maximum traffic can wso2 ESB 5.0.0 can take or hold in a Production environment.
Like how many API's we can deploy in two servers in a cluster with 2 WSO2 MB?
What will be the maximum number of calls each API or the overall API's can take per minute?
We have 2 ESB and 2 MB servers running in a cluster.
ESB: 16 GB RAM 100GB HD
MB: 4 GB RAm 100GB HD
Any information will be helpful.

Related

GCP memorystore redis latency high on 1000 TPS

I am working on GKE and GCP memory store Redis, Redis giving high latency, up to 500 000 requests Redis behavior is as expected, once requests more than 500k, Redis adding more latency and response is very slow.
If you're talking 500K ops/second than that's pretty much what you can expect from a single memory store instance.
You can shard out on the client side or look at other hosted options for Redis on Google cloud that do offer more scaling.

Uploads via InitiateFileTransferToGuest is extreamly slow

The InitiateFileTransferToGuest let's me upload a file to a VM via the ESXi host it's running on.
When I perform the HTTP upload, I'm only getting about 8 Mb/s.
When I use dd on the source machine and target VM, I get about 730 MB/s reads & writes.
When I use iperf between the source machine and target VM, I get 8 Gb/s throughput.
I get the same HTTP upload speed if I use curl or Python's requests module.
All three machines (source, target VM, and ESXi host) are on the same 10 GbE subnet.
Is there some HTTP buffer setting in ESXi that needs adjustment?
What's happening here is that the file is traversing the host and going into the VM with no reliance on the VM's networking configuration. It's using the VM's instance of VMware Tools.
This certainly won't be the most performant option, as you've found already, but it is extremely handy when there are network limitations or the VM is otherwise inaccessible externally, but it is powered on with VMware Tools running.

Restarting 1 Application server(java process) on GCP VM is resulting in bad performance across all Application VMs

I have 3 java applications servers running on GCP VMs. I am getting 2000 TPS.
The URL is a simple GET call to display the log level using actuator end point. I brought down one of the application servers and the load was distributed across other VMs with good TPS. However, the minute I brought up the VM which was shutdown, the performance on all 3 VMs have degraded and my TPS drops to 1000.
Has anyone seen this issue on GCP VMs before? Any information on how to debug further on this?

EC2 instance outgoing http request rate limits

I'm building a node application on EC2 that queries various external APIs several times per second via http requests.
I cannot work this out from the EC2 documentation - are there any EC2 rate limits for querying external APIs?
E.g. if I'm continuously making 2 or 3 http requests per second from an ec2 instance, will I start getting rate limit errors from ec2?
Thanks
ec2 provides you the virtual machine and (if you configure it) the external connection.
Then it's totally up to you on what you query with it.
AWS provides you the layer 3 network which is charged by traffic amount, not number of requests.

WSO2 ESB: Can we count number of hits from the same IP with in the time limit

In WSO2 ESB how can we find the number of hits from the same IP address or the same user is trying to keep our system busy. How can we secure our application in that system.
Is there any feature available in the WSO2 ESB to count the number of hits per IP address or user with in the time limit?
Thanks in advance..
I hope you are talking about Throttling. WSO2 ESB supports Throttling, a mechanism to control access to the services at different levels. You can use IP based throttling for your usecase.