This release of WebLogic Server introduces smart rules. When the policy is triggered - that is, it is evaluated to true - the corresponding scale down action is executed. The policy, named LowMark, is configured to be evaluated every 10 seconds. This action is configured to scale down the dynamic cluster, DynamicCluster, by one server instance. The scale down action, scaleDown, is created. Similarly, Example 7-2 shows the configuration of a policy that, when triggered, executes a scale down action. ScaleUp=wn.createScaleUpAction('scaleUp') ScaleUp=wn.lookupScaleUpAction('scaleUp') When the policy is triggered - that is, it is evaluated to true - the corresponding scale up action is executed.Įxample 7-1 Creating a Policy to Scale Up a Dynamic Cluster The policy, named highMark, is configured to be evaluated every 10 seconds. This action is configured to scale up the dynamic cluster, DynamicCluster, by one server instance. The scale up action, scaleUp, is created. Only one scaling action can be assigned to a given policy.įor example, Example 7-1 shows the WLST commands to create and configure a policy that, when triggered, executes a scale up action. For more information on the scale up and scale down actions, see Chapter 5, "Elastic Actions". WLDF provides two elastic actions, scale up and scale down, that you can assign to a policy to perform a scaling operation. For more information on the Policies and Actions component of WLDF, see " Configuring Policies and Actions" in Configuring and Using the Diagnostics Framework for Oracle WebLogic Server. A policy sets the conditions under which a scaling operation should occur, and when these conditions are met, the scaling action performs the scaling operation.
That shows just how important having a spatial index is.Policy-based scaling is based on policies and associated actions, leveraging the Policies and Actions component of the WebLogic Diagnostics Framework (WLDF). Without spatial index: 85036 milliseconds.Now just to show you why using JMeter is so useful we can now test what the performance would be like if we didn't have a spatial index on that PostGIS table. If we run the plan and look at the Summary Report we can see the results.
#Apache jmeter 2.13 download software
We have then modified our SQL query type to Prepared Select Statement and then changed the SQL query to something similar to what a piece of software would request. So we have added four parameter values ($) and then specified that each is a DECIMAL as a parameter type. Now we need to edit our JDBC request to use the values in the CSV file. We need to give it a name and then specify the location and contents of the CSV file. In your JMeter test plan we need to add a CSV data config so right-click the 'Data Requests' node and choose 'Add | Config Element | CSV Data Set Config' This isn't a very good example of a query that will be made against our database so lets change that now. You can see that 100 Samples were made and the time taken. Now to run this plan we can press the green run button on the toolbar. Right-click the Data Requests node and choose 'Add | Listener | Summary Report' There are lots of different types from Graphs to Tress, at this stage we will just add a Summary Report. We can also add an SQL query just to test the connection works.įinally we need to add a listener to the Plan so that we can see the results of the queries. We need to give it a name, set the Variable Name to the same name as the 'PostGIS Connection' variable name that we set earlier. Right-click the Data Requests node and 'Add | Sampler | JDBC Request' Now that we have setup the database conncection we now need to add a JDBC request. We need to give it a name, a variable name and setup the database connection detailsĭatabase URL: jdbc:postgresql://IPAddress:PortNo/DatabaseName?autoReconnect=true So right-click the Data Requests node and choose 'Add | Config Element | JDBC Connection Configuration' This will add a Thread Group to our plan which we can now configure.Ĭhange the name, number of Threads and the number of Loops In the left-hand side menu, right-click the 'PostGIS Test Plan' and choose 'Add | Threads (Users) | Thread Group option. Now we need to add a Thread Group to our plan, in JMeter a thread is the equivalent to a user.
0 kommentar(er)
