Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 22 additions & 4 deletions labreports/LAB.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@
Course: Messiah College CIS 411, Fall 2018<br/>
Instructors: [Joel Worrall](https://github.com/tangollama) & [Trevor Bunch](https://github.com/trevordbunch)<br/>

Name: YOUR NAME<br/>
Name: Luke Meads<br/>

GitHub: [YOUR_HANDLE](https://github.com/YOUR_HANDLE)<br/>
GitHub: [lukemeads3](https://github.com/lukemeads3)<br/>

# Step 1: Fork this repository
- The URL of my forked repository
Expand All @@ -23,27 +23,45 @@ GitHub: [YOUR_HANDLE](https://github.com/YOUR_HANDLE)<br/>
}
```

{
"data": {
"mutateAccount": {
"id": "a1bd1628-6fa9-46e4-8de2-9d0b89c1e6c1",
"name": "Luke Meads",
"email": "[email protected]"
}
}
}

# Step 3: Signup for and configure New Relic
- The chosen name of your New Relic ```app_name``` configuration
```
app_name: ['<YOUR APP NAME>']
app_name: ['cis411_lab3']
```

# 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?
* What are your observations regarding the performance of this application?
The performance of the application varies on how many items that are requested are returned.
* Is performance even or uneven?
The performance is uneven and all depends on the amount of items that the query applies to
* Between queries and mutations, what requests are less performant?
Mutations have a higher rpm(request per minute) than queries do. My assumption is because mutations are adding something to the file where a query is retrieve information from the file so it has to sort through the whole file.
* Among the less performant requests, which ones are the most problematic?
The query that is coming back with an error when I run it is the accounts(query:"").

# Step 6: Diagnosing an issue based on telemetry data
* Within the transactions you're examining, what segment(s) took the most time?
queryOrdersBySearchTerm was the segment that took the most time.
* Using New Relic, identify and record the least performant request(s).
The query that retrieved all orders that contained the word "everything"
* 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.
queryOrdersBySearchTerm took the most time during this request taking 2,780 ms to perform the task while the next longest was 424 ms by Expressjs.
* Recommend a solution for improving the performance of those most problematic request(s) / permiatation(s).
To improve the performance of the queries, I would suggest to redesign the database with better organization.

# Step 7: Submitting a Pull Request
_Note: No lab notes required._
Expand Down
96 changes: 54 additions & 42 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@
"graphql": "^14.0.2",
"lodash.startcase": "^4.4.0",
"lokijs": "^1.5.5",
"newrelic": "^4.9.0",
"newrelic": "^4.13.1",
"uuid": "^3.3.2"
},
"devDependencies": {
Expand Down