Home/ Questions/Q 8267107
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T05:23:53+00:00

Currently I have a working solution using threads (a new thread is instantiated and

  • 0

Currently I have a working solution using threads (a new thread is instantiated and run for each image), but I read everywhere that threads are memory expensive and to better use other solutions in Android. But not quite sure what fits better for this case (AsynchTask, a thread pool, or …?). The grid is scrollable, and if I scroll fast I’ll be instantiating hundreds of threads at the same time…

One thing which helps is to cache the images, so the threads are just created and run the first time. But anyways, I would like to optimize this first loading.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think one extra thread should be enough..I am maybe wrong, but you will have UI thread which would handle UI rendering and so on and then an AsyncTask for loading images (or thread). There you can instantiate as much parallel donwloads as possible and after each one is loaded you can send a message to the UI thread an update GridList..

    Actually when you will use some other Library for HTTP connection, it would instantiate extra thread (or asynctask) for each donwload.

    I have been working with this one and it works flawlessly .

    • 0