Goal
Evaluate Toolforge capabilities and their impact on hosting the image suggestions api service. Consider implications for hosting future PoC services
Acceptance Criteria
- Determine CPU constraints and associated impact on the image suggestions api service needs
- Determine memory constraints and associated impact on the image suggestions api service needs
- Extrapolate findings to provide guidance for future possible services
- Document all findings on-wiki
The findings from T280849: [SPIKE] Evaluate toolforge performance capabilities and limitations and T280851: [SPIKE] Explore sqlite query planner behavior may be helpful for this task.
The results of this analysis should be compared and contrasted with the results from T280850: [SPIKE] Evaluate Cloud VPS performance capabilities and limitations
The Toolforge documentation spells out certain limitations and constraints: documentation
This task is about contextualizing that information. Regarding the image suggestion api, what operations have proven to be most affected by these limitations? Are there any reasonable mitigations or workarounds that could be implemented? Regarding future services, what questions should implementors of future services consider when deciding whether or not to use Toolforge? What characteristics of future services might make Toolforge an appropriate or inappropriate choice?