This is related to #966 : with current Javascript algorithm, we cut the photos set in blocks (which is fine) but then we launch all blocks at the same time.
This may lead to too many requests at the same time (imagine 1,000,000 photos in your set, that would make 1,000 simultaneous ajax requests) and make the whole sync slower than before.
... instead of sequentially.
This is related to #966 : with current Javascript algorithm, we cut the photos set in blocks (which is fine) but then we launch all blocks at the same time.
This may lead to too many requests at the same time (imagine 1,000,000 photos in your set, that would make 1,000 simultaneous ajax requests) and make the whole sync slower than before.
<!-- github-sync-id:488647495 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
... instead of sequentially.
This is related to #966 : with current Javascript algorithm, we cut the photos set in blocks (which is fine) but then we launch all blocks at the same time.
This may lead to too many requests at the same time (imagine 1,000,000 photos in your set, that would make 1,000 simultaneous ajax requests) and make the whole sync slower than before.