Last couple of weeks I was busy preparing to my OOW'17 session about estimating Java Cloud Service performance for ADF application. I was running stress tests against various JCS instance configurations to be able to create performance estimation methodology. I will describe this methodology on OOW, but here today will list key steps required to scale up JCS instance.
Let's assume you are running single cloud node with 1 CPU and 7.5 GB RAM. This node contains WLS admin and managed server:
To scale up cloud node, simply invoke Scale Up command from the menu. Select new compute shape and confirm scale up operation:
Scale up completed:
Now go to WebLogic console and update Managed Server startup parameters, to adjust heap size to higher value:
Managed server memory can be increased up to certain amount. If more resources will be needed, at some point you will need to create multiple managed servers and connect them into cluster. This would require to define Load Balancer instance (to have single entry point to the cluster):
Cluster node must run in dedicated cloud node. If cluster is based on two managed servers, there must be two cloud nodes:
Managed servers from cloud nodes can be connected into single cluster, this can be done in WebLogic console:
Once cluster is defined, deployment becomes easy - you can deploy ADF application into cluster and it will be propagated to all nodes:
Traffic director running in load balancer instance will be automatically configured to route traffic to cluster nodes:
Let's assume you are running single cloud node with 1 CPU and 7.5 GB RAM. This node contains WLS admin and managed server:
To scale up cloud node, simply invoke Scale Up command from the menu. Select new compute shape and confirm scale up operation:
Scale up completed:
Now go to WebLogic console and update Managed Server startup parameters, to adjust heap size to higher value:
Managed server memory can be increased up to certain amount. If more resources will be needed, at some point you will need to create multiple managed servers and connect them into cluster. This would require to define Load Balancer instance (to have single entry point to the cluster):
Cluster node must run in dedicated cloud node. If cluster is based on two managed servers, there must be two cloud nodes:
Managed servers from cloud nodes can be connected into single cluster, this can be done in WebLogic console:
Once cluster is defined, deployment becomes easy - you can deploy ADF application into cluster and it will be propagated to all nodes:
Traffic director running in load balancer instance will be automatically configured to route traffic to cluster nodes:
No comments:
Post a Comment