benjaminramey/ObsidianJournal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2024-10-24 12:41:53

Browse Source
This commit is contained in:
Benjamin Ramey
2024-10-24 12:41:53 -05:00
parent 66943c7bae
commit e4bbc8bf4b
2 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Daily Notes/2024/10/2024-10-21 (Monday).md Normal file
View File

@@ -0,0 +1,4 @@
# Work
- [ ] Check on Content API CPU usage (see [[2024-10-24 (Thursday)]])
- [ ]
# Meetings

2
Daily Notes/2024/10/2024-10-24 (Thursday).md
View File

@@ -2,7 +2,7 @@
- [ ] Finish [[skeletor]] asyncification - [ ] Finish [[skeletor]] asyncification
- [ ] Estimate effort for verbum launch: https://faithlife.slack.com/archives/C07MHA5BH08/p1729713421056869 - [ ] Estimate effort for verbum launch: https://faithlife.slack.com/archives/C07MHA5BH08/p1729713421056869
- [ ] Help German team figure out why gifted subscription doesn't appear for receiving user in their list of subscriptions: https://faithlife.slack.com/archives/C03R1MQSR51/p1729680712833219 - [ ] Help German team figure out why gifted subscription doesn't appear for receiving user in their list of subscriptions: https://faithlife.slack.com/archives/C03R1MQSR51/p1729680712833219
- [ ] Weird Content API CPU spike and drop: https://portal.azure.com/#@faithlife.com/resource/subscriptions/19ac6e33-f9db-4c5a-9b09-90348e9025e0/resourceGroups/CommerceTenant/providers/Microsoft.Insights/components/fl-cmrc-wus2-appi-contentapiv1/metricsV2 - [ ] Weird Content API CPU spike and drop: https://portal.azure.com/#@faithlife.com/resource/subscriptions/19ac6e33-f9db-4c5a-9b09-90348e9025e0/resourceGroups/CommerceTenant/providers/Microsoft.Insights/components/fl-cmrc-wus2-appi-contentapiv1/metricsV2. Check on the CPU usage on [[2024-10-21 (Monday)]] to see if it's exhibiting the same behavior.
# Meetings # Meetings
## Algolia ## Algolia
- [ ] Find out how large indexable records would be if we put _all_ users IDs and _all_ authors, etc on on a single record - [ ] Find out how large indexable records would be if we put _all_ users IDs and _all_ authors, etc on on a single record