secondlife / secondlife/viewer
Async Inventory: Improve Login Performance via Asynchronous Loading
- Dominant language
- C++
- Stars
- 299
- Forks
- 146
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 88
Description
What does this feature/enhancement do? Why is it needed?
This sub-issue coordinates validation and monitoring for the asynchronous inventory loading proposed in PR #4893. By moving inventory skeleton hydration and essentials fetch to an asynchronous workflow, login times are expected to improve, especially for residents with large inventories.
Key areas of focus:
- Confirm login speed increases by asynchronously loading inventory data
- Ensure user-facing inventory is accurate and complete post-login
- Test large inventory scenarios (100k+ items), edge cases, and cache integrity
- Follow regression scenarios to confirm no issues in folder hierarchy or item order
Reference: Async Inventory Loading Implementation PR #4893
Parent Issue: Quality of Life (#4969)
This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting
/reward 100 (replace 100 with the amount).🕵️♂️ If someone starts working on this issue to earn the rewards, they can comment
/try to let everyone know!🙌 And when they open the PR, they can comment
/claim #4972 either in the PR description or in a PR's comment.🪙 Also, everyone can tip any user commenting
/tip 20 @Geenz (replace 20 with the amount, and @Geenz with the user to tip).📖 If you want to learn more, check out our documentation.
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
Start by reviewing the asynchronous inventory loading implementation in PR #4893 and the validation goals listed here. Test login performance and inventory completeness with 100k+ items, then check cache integrity, folder hierarchy, item order, and regression scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100