可展开RecyclerView中ListView渲染缓慢的性能问题求助

Hey, let's break down why you're seeing slow rendering and fix this step by step!

The core issue here is that you're instantiating and setting up a ListView (plus its ArrayAdapter) every time onBindViewHolder gets called. Remember, onBindViewHolder runs constantly as the RecyclerView scrolls (it's how ViewHolder reuse works), so you're creating a brand new ListView instance over and over—even when the ListView is invisible. That's a huge waste of CPU and memory, which directly causes your rendering jank.

Here are concrete fixes you can implement right away:

1. Move ListView initialization to the ViewHolder (reuse, don't recreate) #

Instead of creating the ListView in onBindViewHolder, set it up once in your RecyclerView ViewHolder's constructor. Then, in onBindViewHolder, you only update the ListView's data, not the entire view or adapter.

Example code snippet:

// Inside your RecyclerView ViewHolder class
class MyViewHolder(itemView: View) : RecyclerView.ViewHolder(itemView) {
    val nestedListView: ListView = itemView.findViewById(R.id.nested_list)
    private val listAdapter: ArrayAdapter<String> = ArrayAdapter(
        itemView.context,
        R.layout.your_checked_text_layout,
        emptyList() // Initialize with empty data first
    )

    init {
        // Set up the ListView once here
        nestedListView.adapter = listAdapter
        nestedListView.visibility = View.GONE // Keep it invisible initially
    }

    // Call this in onBindViewHolder to update data
    fun bindData(nestedItems: List<String>) {
        listAdapter.clear()
        listAdapter.addAll(nestedItems)
        // No need to re-set the adapter every time!
    }
}

// In your RecyclerView Adapter's onBindViewHolder
override fun onBindViewHolder(holder: MyViewHolder, position: Int) {
    val item = yourDataList[position]
    holder.bindData(item.nestedStrings)
    // ... other binding logic
}

This way, you reuse the same ListView and Adapter instance every time the ViewHolder is recycled—no more repeated instantiation overhead.

2. Lazy-load the ListView (only initialize when needed) #

Since the ListView starts invisible, there's no reason to set it up until the user actually needs to see it (e.g., when they tap to expand the item).

• Add a click listener to your RecyclerView item that toggles the ListView's visibility.
• Only initialize the ListView and its adapter the first time the user triggers the expand action.

Example:

// In your ViewHolder's init block
itemView.setOnClickListener {
    if (nestedListView.visibility == View.GONE) {
        // First time expanding: initialize if not already done
        if (listAdapter.count == 0) {
            // Assume you've stored the nested data in the ViewHolder or passed it in
            listAdapter.addAll(storedNestedData)
        }
        nestedListView.visibility = View.VISIBLE
    } else {
        nestedListView.visibility = View.GONE
    }
}

This defers all the ListView setup work until it's actually necessary, so your RecyclerView initializes and scrolls much faster.

3. Replace ListView with a RecyclerView (better nested performance) #

ListView isn't optimized for nested scrolling and has less efficient view reuse compared to RecyclerView. Swapping the nested ListView for a lightweight RecyclerView will give you better overall performance, especially if your nested lists are long.

You can use a simple LinearLayoutManager and a basic Adapter for the nested RecyclerView—since you're just displaying strings with a CheckedTextView, the code change is minimal.

4. Optimize your layout hierarchy #

Check the layout you're using for the nested ListView's item (your_checked_text_layout). Make sure there are no unnecessary nested ViewGroups. For example, if your CheckedTextView is wrapped in a LinearLayout that doesn't add any value, remove it. A flatter layout means faster measure and layout passes during rendering.

5. Cache your ArrayAdapter instances #

If multiple RecyclerView items use the same type of nested list, you can cache ArrayAdapter instances (or even the entire nested RecyclerView Adapter) to avoid recreating them. This is especially useful if your nested data is static or reused across items.

By implementing these changes, you'll eliminate the repeated view creation overhead that's causing your slow rendering. Start with the first two fixes—they'll give you the biggest performance boost with the least code change!

内容的提问来源于stack exchange，提问作者Manuel Pepe