lisawray/groupie

Profile counting requests and possibly add caching / lookup structure

Open

#91 opened on May 29, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (3,627 stars) (295 forks)batch import
enhancementhelp wanted

Description

Groupie makes a lot of requests to methods like getIndex(Item) which internally iterate through all the children of a group. In practice, this is rarely problematic, but it could become an issue with very deeply nested groups and items at the end of extremely long lists.

Contributor guide

Tech stack
javaandroid
Domain
performance
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaAndroid RecyclerViewGroupie library basicsProfiling tools (e.g., Android Studio Profiler)
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Start by profiling the getIndex(Item) method to measure its performance impact with deeply nested groups. Look at the Groupie source code, specifically the Group and Item classes, to understand the current iteration logic. Consider implementing a HashMap based lookup to avoid linear scans, and evaluate memory overhead. Review existing comments in the issue for any prior suggestions. No linked PRs or maintainer clarification needed.