microsoft / microsoft/simplechat
Evaluate server-side template rendering and caching strategy for profile metrics
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 152
- Forks
- 116
- Avg merge
- 7h 7m
- Merged PRs (30d)
- 122
Description
### Background
The profile page currently performs data-heavy calls to populate personal metrics. This raises questions about performance, caching strategy, and whether metrics should be live or precomputed.
### Proposal
Consider updating the Python and Jinja renderTemplate flow to perform data-heavy queries during server-side rendering and cache results per user when the profile page is accessed. This could reduce repeated client-side or API calls and improve perceived load time.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing the Python and Jinja renderTemplate flow and the profile metrics calls, then compare live, server-rendered, and per-user cached approaches. Done requires an agreed strategy and defined performance and freshness criteria, which the issue does not yet specify.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100