diff --git a/labreports/LAB.md b/labreports/LAB.md deleted file mode 100644 index 2ae1eee9..00000000 --- a/labreports/LAB.md +++ /dev/null @@ -1,55 +0,0 @@ -# Lab Report Template for CIS411_Lab3 -Course: Messiah College CIS 411, Fall 2018
-Instructors: [Joel Worrall](https://github.com/tangollama) & [Trevor Bunch](https://github.com/trevordbunch)
- -Name: YOUR NAME
- -GitHub: [YOUR_HANDLE](https://github.com/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: [''] -``` - -# 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**. -2. Check in those changes and **note your solution(s)** in your lab report. \ No newline at end of file diff --git a/labreports/LAB3_ETHANWWM.md b/labreports/LAB3_ETHANWWM.md new file mode 100644 index 00000000..b3f5a023 --- /dev/null +++ b/labreports/LAB3_ETHANWWM.md @@ -0,0 +1,97 @@ +# Lab Report Template for CIS411_Lab3 + +Course: Messiah College CIS 411, Fall 2018
+ +Instructors: [Joel Worrall](https://github.com/tangollama) & [Trevor Bunch](https://github.com/trevordbunch)
+ +Name: Ethan Wong
+ +GitHub: [ethanwwm](https://github.com/ethanwwm)
+ +# Step 1: Fork this repository + +[https://github.com/ethanwwm/cis411_lab3](https://github.com/ethanwwm/cis411_lab3) + +# 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": "0693a4c8-eec1-41ba-bea9-1cddc9feba50", + "name": "Ethan Wong", + "email": "ethanwwm@gmail.com" + } + } +} +``` + +# Step 3: Signup for and configure New Relic + +- The chosen name of your New Relic `app_name` configuration + +``` + +app_name: ['cislab'] + +``` + +# 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? \* The queries ran smoothly even though the return time varied for each of them. + +- Is performance even or uneven? \* Uneven. + +- Between queries and mutations, what requests are less performant? \* Queries. + +- Among the less performant requests, which ones are the most problematic? \* The queries that have too broad of a search scope can cause a significant drop in performance. + +# Step 6: Diagnosing an issue based on telemetry data + +- Within the transactions you're examining, what segment(s) took the most time? \* When searching for Strings instead of being specific to the item in a category can be much slower. + +- Using New Relic, identify and record the least performant request(s). + +``` + +``` + +{ +#all accounts that contain gmail.com +accounts(query: "gmail.com") { +id +items { +label +quantity +} +} +} + +``` + +``` + +- 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. \* queryOrderBySearchTerm and Remainder component + +- Recommend a solution for improving the performance of those most problematic request(s) / permiatation(s). \* Basically be more specific with your queries than being so general. + +# 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. diff --git a/package-lock.json b/package-lock.json index cc9fe249..f9753cc9 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1288,6 +1288,7 @@ "version": "0.1.4", "bundled": true, "dev": true, + "optional": true, "requires": { "kind-of": "^3.0.2", "longest": "^1.0.1", @@ -1612,7 +1613,8 @@ "is-buffer": { "version": "1.1.6", "bundled": true, - "dev": true + "dev": true, + "optional": true }, "is-builtin-module": { "version": "1.0.0", @@ -1696,6 +1698,7 @@ "version": "3.2.2", "bundled": true, "dev": true, + "optional": true, "requires": { "is-buffer": "^1.1.5" } @@ -1742,7 +1745,8 @@ "longest": { "version": "1.0.1", "bundled": true, - "dev": true + "dev": true, + "optional": true }, "lru-cache": { "version": "4.1.3", @@ -2008,7 +2012,8 @@ "repeat-string": { "version": "1.6.1", "bundled": true, - "dev": true + "dev": true, + "optional": true }, "require-directory": { "version": "2.1.1",