Skip to content

Latest commit

 

History

History
55 lines (44 loc) · 2.08 KB

LAB.md

File metadata and controls

55 lines (44 loc) · 2.08 KB

Lab Report Template for CIS411_Lab3

Course: Messiah College CIS 411, Fall 2018
Instructors: Joel Worrall & Trevor Bunch

Name: YOUR NAME

GitHub: YOUR_HANDLE

Step 1: Fork this repository

  • The URL of my forked repository

Step 2: Clone your forked repository from the command line

  • My GraphQL response from adding myself as an account on the test project
{
  "data": {
    "mutateAccount": {
      "id": "a10db030-ded8-4397-a78f-30b79d3497ab",
      "name": "MY NAME",
      "email": "MY EMAIL"
    }
  }
}

Step 3: Signup for and configure New Relic

  • The chosen name of your New Relic app_name configuration
app_name: ['<YOUR APP NAME>']

Step 4: Exercising the application / generating performance data

Note: No lab notes required.

Step 5: Explore your performance data

  • What are your observations regarding the performance of this application?
  • Is performance even or uneven?
  • Between queries and mutations, what requests are less performant?
  • Among the less performant requests, which ones are the most problematic?

Step 6: Diagnosing an issue based on telemetry data

  • Within the transactions you're examining, what segment(s) took the most time?
  • Using New Relic, identify and record the least performant request(s).
  • Using the Transaction Trace capability in New Relic, identify which segment(s) in that request permiatation is/are the most problematic and record your findings.
  • Recommend a solution for improving the performance of those most problematic request(s) / permiatation(s).

Step 7: Submitting a Pull Request

Note: No lab notes required.

Step 8: [EXTRA CREDIT] Address the performance issue(s)

For the purposes of gaining 25% extra credit on the assignment, perform any of the following:

  1. Adjust the diagnosed slow call(s) to improve performance.
  2. Verify the improved performance in New Relic, including data and/or screenshots in your lab report.
  3. Check in those changes and note your solution(s) in your lab report.