Walmart Caching Meeting

* Points about where drop is occurring - DMS or... App? (Unsure what this means)
* Ece confirmed that this is happening from DMS - awaiting a team member to join
* Rafi stressed importance of AE and that this _cannot_ occur during AE.
* Sanjeev is not from DMS team but showed us the app and HelpMenu. I explained where the caching is needed.
* Caching is not needed on webview but on the course list show prior to webview.
* Jess brought up important point that there would need to be caching per driver per category (possibility of tens of cached results)
* Minal and Harbiner from DMS joined the call and we went over the same items.
* Minal disagreed that caching would solve this. We explained the last P0/P1.
* DMS team thinks the increase in traffic are real users coming to help center due to outage.
  * We will need to confirm if the numbers are "real". Norm to ping Krystal to get confirmation of numbers.
* Ece needs to confirm with Eng how long any of this will take and if it's possible before code freeze.
* Possible "middle of the road" solution:
	* Walmart to implement caching for /helpMenu courses
	* Northpass to increase load workers during AE
* Remaining questions from Northpass:
	* Sandeep saw the 499 requests in logs and the connections were cut _way before_ the 5s timeout. This is something odd on the WMT side.
	* If the traffic is from real drivers, why do all the logs during the P1 show "WARN" (yellow) instead of the regular green, normal calls.
* Walmart team to confirm numbers of drivers during outage that landed on the helpmenu.
* Walmart team to estimate how long it would take to implement caching.
* Norm to email Walmart team after speaking with our engineering team about increases worker load during AE.
