This post continues the series about from AWS ALB Price Planning w/ IIS : Active Connections. Here are couple things to note about the query to grab Bandwidth:
- This is one thing that IIS logs can accurately evaluate. You can get the number of bytes sent and received through an IIS/ARR proxy server by turning on the cs-bytes and sc-bytes W3C logging values. (see screen shot below)
- AWS does that pricing based on average usage per hour. So, the sql will aggregate the data into hour increments in order to return results.
Bandwidth SQL Script
Graphing the output from the script shows:
- Mbps per Hour (for a month)
- The jump in the average number of new connections in the beginning of the month corresponded to a return of students to campus. During the beginning of the month, school was not in session and then students returned.
- The dip at the end of the month has to do with a mistake I made loading some data. There is one of data that I forgot to import the IIS logs, but I don’t really want to go back and correct the data. It will disappear from the database in about a month.
- Mbps per Hour LCUs
- This is a critical number. We put 215+ websites through the proxy server. The two AWS ALB dimensions that will have the biggest impact on the price (the number of LCUs) will be the Bandwidth usage and the Rule Evaluations.
- I’m very surprised that the average LCUs per hour for a month is around 2.3 LCUs, which is very low.
Next Up, AWS ALB Price Planning w/ IIS : Rule Evaluations.
0 comments:
Post a Comment