docs: SQLite write bottleneck #17

TobiasGleiter · TobiasGleiter · commit bc26fd15fcc4 · 2025-10-10T19:31:11.000-04:00
diff --git a/wiki/README.md b/wiki/README.md
@@ -60,4 +60,4 @@ erDiagram
 
 ## Scaling
 
-Before scaling any services it is recommend to scale the hardware. Go can handle many requests with less CPU and RAM usage. After that, it is useful to identify the bottlenecks of the app. Which can be found in Issue [#16](https://github.com/bit8bytes/goalkeepr/issues/16).
+Before scaling any services it is recommend to scale the hardware. Go can handle many requests with less CPU and RAM usage. After that, it is useful to identify the bottlenecks of the app. Which can be found in Issue [#16](https://github.com/bit8bytes/goalkeepr/issues/16). One predictable bottleneck will be SQLite, particularly the write operations.

Original file line number	Diff line number	Diff line change
`@@ -60,4 +60,4 @@ erDiagram`
`60`	`60`
`61`	`61`	`## Scaling`
`62`	`62`
`63`		`-Before scaling any services it is recommend to scale the hardware. Go can handle many requests with less CPU and RAM usage. After that, it is useful to identify the bottlenecks of the app. Which can be found in Issue [#16](https://github.com/bit8bytes/goalkeepr/issues/16).`
	`63`	`+Before scaling any services it is recommend to scale the hardware. Go can handle many requests with less CPU and RAM usage. After that, it is useful to identify the bottlenecks of the app. Which can be found in Issue [#16](https://github.com/bit8bytes/goalkeepr/issues/16). One predictable bottleneck will be SQLite, particularly the write operations.`