StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15792133
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-04-03T15:54:45.887
FavoriteCount
0
LastActivityDate
2013-04-03T15:54:45.887
LastEditDate
2017-04-13T12:13:43.650
LastEditorUserId
-1
OwnerUserId
45773
ParentId
15789166
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
That's a fairly complicated topic, mostly due to the <a href="http://aws.amazon.com/elasticloadbalancing/" rel="nofollow noreferrer">Amazon ELB</a> routing documentation falling short of being non existent, so one needs to assemble some pieces to draw a conclusion - see my answer to the related question <a href="https://serverfault.com/a/386527/10305">Can Elastic Load Balancers correctly distribute traffic to different size instances</a> for a detailed analysis including all the references I'm aware of. For the question at hand I think it boils down to the somewhat vague AWS team response from 2009 to <a href="https://forums.aws.amazon.com/message.jspa?messageID=129199#129199" rel="nofollow noreferrer">ELB Strategy</a>: <blockquote> ELB loosely keeps track of how many requests (or connections in the case of TCP) are outstanding at each instance. It does not monitor resource usage (such as CPU or memory) at each instance. ELB currently will round-robin amongst those instances that it believes has the fewest outstanding requests. [emphasis mine] </blockquote> Depending on your application architecture and request variety, larger <a href="http://aws.amazon.com/ec2/instance-types/" rel="nofollow noreferrer">Amazon EC2 instance types</a> might be able to serve requests faster, thus have less outstanding requests and receive more traffic accordingly, but either way the ELB supposedly distributes traffic appropriately on average, i.e. should implicitly account for the uneven instance characteristics to some extent - I haven't tried this myself though and would recommend both, <a href="http://docs.amazonwebservices.com/ElasticLoadBalancing/latest/DeveloperGuide/US_MonitoringLoadBalancerWithCW.html" rel="nofollow noreferrer">Monitoring Your Load Balancer Using CloudWatch</a> as well as monitoring your individual EC2 instances and correlate the results in order to gain respective insight and confidence into such a setup eventually.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow Amazon ELB will distribute requests to Amazon EC2 instances of different instance types?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USSteffen Opel
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow Amazon ELB will distribute requests to Amazon EC2 instances of different instance types?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.