Azure Client Details

Author
Ujwala Tambe & Pranit Mhatre
Schema Description
  • Data is stored in tables: "users", "resources", "pendfriendship", "conffriendship" and "manipulation".
  • Friendship records are stored in two tables, "pendfriendship" and "conffriendship", where there is only one record for a pending friendship and two records for confirmed friendships.
  • Profile and thumbnail images for a user are stored as arrays of bytes in Azure's Blob storage space.
Index Structures
  • The "resources" table is indexed on resourceid and walluserid (the userid for the wall, where the resource is posted on).
  • The "manipulation" table is indexed on manipulationid and resourceid.
  • The "conffriendship" and "pendfriendship" tables are indexed on inviteeid and inviterid.
Database Load Time
(10 Load Threads)
  • 10,000 members, 100 friends per user, 100 resources per user, no user images: 15 Minutes
  • 10,000 members, 100 friends per user, 100 resources per user, 12KB profile images and 2KB thumbnail images: 22 Minutes
SoAR Rating# †
10,000 members, 100 friends per user, 100 resources per user, no user images
  • VeryLowUpdateActions: 5277 actions/sec
  • LowUpdateActions: 5352 actions/sec
  • HighUpdateActions: 5230 actions/sec
Source
Download

# 10,000 members, 100 friends per user, 100 resources per user, no user images.

† The reported performance numbers were obtained using Amazon EC2 instances with the following specifications: M1 Extra Large instances, 8 ECUs, 4 cores, 15 Gigabyte. One instance hosted the data store while multiple BGClients were used to generate workload. Processor and network resources of the BGClients were not a bottleneck while obtaining these numbers.