我正在迁移一个应用程序从v3滑行v4.7.1并注意到FifoPriorityThreadPoolExecutor类已被删除。我们使用它来限制Glide用于进行网络操作的线程数。
旧代码
public class GlideConfiguration implements GlideModule {
@Override
public void applyOptions(Context context, GlideBuilder builder) {
builder.setResizeService(new FifoPriorityThreadPoolExecutor(1));
}
...
}
新代码
@GlideModule
public class MyAppGlideModule extends AppGlideModule {
private static final String FIFO_SOURCE_EXECUTOR_NAME = "fifo-source";
@Override
public void applyOptions(@NonNull Context context, @NonNull GlideBuilder builder) {
builder.setSourceExecutor(newSourceExecutor(1, FIFO_SOURCE_EXECUTOR_NAME, GlideExecutor.UncaughtThrowableStrategy.DEFAULT));
}
...
}
但它仍然使用4个线程。我究竟做错了什么?
检查滑翔的源代码后。只有在未向构建器提供源执行程序时,Glide才会初始化其默认源执行程序。
Glide build(@NonNull Context context) {
if (sourceExecutor == null) {
sourceExecutor = GlideExecutor.newSourceExecutor();
}
if (diskCacheExecutor == null) {
diskCacheExecutor = GlideExecutor.newDiskCacheExecutor();
}
if (animationExecutor == null) {
animationExecutor = GlideExecutor.newAnimationExecutor();
}
...
}
// Glide executor is simply a wrapper over ThreadPoolExecutor class.
public static GlideExecutor newSourceExecutor(int threadCount, String name, UncaughtThrowableStrategy uncaughtThrowableStrategy) {
return new GlideExecutor(new ThreadPoolExecutor(threadCount /* corePoolSize */,threadCount /* maximumPoolSize */,0 /* keepAliveTime */,TimeUnit.MILLISECONDS,new PriorityBlockingQueue<Runnable>(),new DefaultThreadFactory(name, uncaughtThrowableStrategy, false)));
}
因为您正在使用Stetho库检查线程以监视网络调用,该调用不显示有关线程的任何信息。这些请求很可能是由单线程发起的。
为了更好地理解应用程序中的线程使用情况,您应该使用Android monitor -> DDMS -> Threads.
进行检查