std::async function running serially

后端 未结 3 1869
自闭症患者
自闭症患者 2021-01-24 04:22

When using std::async with launch::async in a for loop, my code runs serially in the same thread, as if each async call waits for the previous before launching. In the notes for

相关标签:
3条回答
  • 2021-01-24 04:51

    That's a misfeature of std::async as defined by C++11. Its futures' destructors are special and wait for the operation to finish. More detailed info on Scott's Meyers blog.

    cache is being destroyed at the end of each loop iteration, thereby calling destructors of its subobjects.

    Use packaged_task or ensure you keep a container of copies of shared pointers to your cache to avoid waiting for the destructors. Personally, I'd go with packeged_task

    0 讨论(0)
  • 2021-01-24 04:51

    As you noticed yourself, the future d-tor of future returned by std::async blocks and waits for the async operation to finish (for the future to become ready). In your case, cache object goes out of scope at each of the loop iterations and thus gets destructed, together with the future it holds, so you see the mentioned effect.

    0 讨论(0)
  • 2021-01-24 05:05

    The std::future returned by async blocks in the destructor. That means when you reach the } of

    for(uint64_t start: chunksToDownload){
        DownloadItem cache = std::make_shared<__DownloadItem__>();
        cache->last_access = time(NULL);
        cache->future =
                std::async(std::launch::async, &FileIO::download, this, api,cache, cacheName, start, start + BLOCK_DOWNLOAD_SIZE - 1);
     }  // <-- When we get here
    

    cache is destroyed which in turn calls the destructor offuture which waits for the thread to finish.

    What you need to do is store each future returned from async in a separate persistent future that is declared outside of the for loop.

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