CompletableFuture allof(..).join() vs CompletableFuture.join()

前端 未结 1 2098
感情败类
感情败类 2020-12-18 11:29

I am currently using CompletableFuture supplyAsync() method for submitting some tasks to common thread pool. Here is what code snippet looks like:

final List         


        
相关标签:
1条回答
  • 2020-12-18 11:44

    First of all, .getNow() does not work, as this method requires a fall-back value as argument for the case the future is not completed yet. Since you are assuming the future to be completed here, you should also use join().

    Then, there is no difference regarding thread exhaustion as in either case, you are waiting for the completion of all jobs before proceeding, potentially blocking the current thread.

    The only way to avoid that, is by refactoring the code to not expect a result synchronously, but rather schedule the subsequent processing action to do done, when all jobs have been completed. Then, using allOf becomes relevant:

    final List<CompletableFuture<List<Test>>> completableFutures = resolvers.stream()
        .map(resolver -> supplyAsync(() -> task.doWork()))
        .collect(toList());
    
    CompletableFuture.allOf(completableFutures.toArray(new CompletableFuture<?>[0]))
        .thenAccept(justVoid -> {
            // here, all jobs have been completed
            final List<Test> tests = completableFutures.stream()
                .flatMap(completableFuture -> completableFuture.join().stream())
                .collect(toList());
            // process the result here
        });
    

    By the way, regarding the toArray method on collections, I recommended reading Arrays of Wisdom of the Ancients…

    0 讨论(0)
提交回复
热议问题