java 合并2个有序列,RxJava合并请求序列

The Problem

I have two Apis. Api 1 gives me a List of Items and Api 2 gives me more detailed Information for each of the items I got from Api 1. The way I solved it so far results in bad Performance.

The Question

Efficent and fast solution to this Problem with the help of Retrofit and RxJava.

My Approach

At the Moment my Solution Looks like this:

Step 1: Retrofit executes Single> from Api 1.

Step 2: I iterate through this Items and make a request for each to Api 2.

Step 3: Retrofit Returns Sequentially executes Single for

each item

Step 4: After all calls form Api 2 completely executed I create a new Object for all Items combining the Information and Extended Information.

My Code

public void addExtendedInformations(final Information[] informations) {

final ArrayList informationDetailArrayList = new ArrayList<>();

final JSONRequestRatingHelper.RatingRequestListener ratingRequestListener = new JSONRequestRatingHelper.RatingRequestListener() {

@Override

public void onDownloadFinished(Information baseInformation, ExtendedInformation extendedInformation) {

informationDetailArrayList.add(new InformationDetail(baseInformation, extendedInformation));

if (informationDetailArrayList.size() >= informations.length){

listener.onAllExtendedInformationLoadedAndCombined(informationDetailArrayList);

}

}

};

for (Information information : informations) {

getExtendedInformation(ratingRequestListener, information);

}

}

public void getRatingsByTitle(final JSONRequestRatingHelper.RatingRequestListener ratingRequestListener, final Information information) {

Single repos = service.findForTitle(information.title);

disposable.add(repos.subscribeOn(Schedulers.io()).observeOn(AndroidSchedulers.mainThread()).subscribeWith(new DisposableSingleObserver() {

@Override

public void onSuccess(ExtendedInformation extendedInformation) {

ratingRequestListener.onDownloadFinished(information, extendedInformation);

}

@Override

public void onError(Throwable e) {

ExtendedInformation extendedInformation = new ExtendedInformation();

ratingRequestListener.onDownloadFinished(extendedInformation, information);

}

}));

}

public interface RatingRequestListener {

void onDownloadFinished(Information information, ExtendedInformation extendedInformation);

}

解决方案

tl;dr use concatMapEager or flatMap and execute sub-calls asynchronously or on a schedulers.

long story

I'm not an android developer, so my question will be limited to pure RxJava (version 1 and version 2).

If I get the picture right the needed flow is :

some query param

\--> Execute query on API_1 -> list of items

|-> Execute query for item 1 on API_2 -> extended info of item1

|-> Execute query for item 2 on API_2 -> extended info of item1

|-> Execute query for item 3 on API_2 -> extended info of item1

...

\-> Execute query for item n on API_2 -> extended info of item1

\----------------------------------------------------------------------/

|

\--> stream (or list) of extended item info for the query param

Assuming Retrofit generated the clients for

interface Api1 {

@GET("/api1") Observable> items(@Query("param") String param);

}

interface Api2 {

@GET("/api2/{item_id}") Observable extendedInfo(@Path("item_id") String item_id);

}

If the order of the item is not important, then it is possible to use flatMap only:

api1.items(queryParam)

.flatMap(itemList -> Observable.fromIterable(itemList)))

.flatMap(item -> api2.extendedInfo(item.id()))

.subscribe(...)

But only if the retrofit builder is configured with

Either with the async adapter (calls will be queued in the okhttp internal executor). I personally think this is not a good idea, because you don't have control over this executor.

.addCallAdapterFactory(RxJava2CallAdapterFactory.createAsync()

Or with the scheduler based adapter (calls will be scheduled on the RxJava scheduler). It would my preferred option, because you explicitly choose which scheduler is used, it will be most likely the IO scheduler, but you are free to try a different one.

.addCallAdapterFactory(RxJava2CallAdapterFactory.createWithScheduler(Schedulers.io()))

The reason is that flatMap will subscribe to each observable created by api2.extendedInfo(...) and merge them in the resulting observable. So results will appear in the order they are received.

If the retrofit client is not set to be async or set to run on a scheduler, it is possible to set one :

api1.items(queryParam)

.flatMap(itemList -> Observable.fromIterable(itemList)))

.flatMap(item -> api2.extendedInfo(item.id()).subscribeOn(Schedulers.io()))

.subscribe(...)

This structure is almost identical to the previous one execpts it indicates locally on which scheduler each api2.extendedInfo is supposed to run.

It is possible to tune the maxConcurrency parameter of flatMap to control how many request you want to perform at the same time. Although I'd be cautious on this one, you don't want run all queries at the same time. Usually the default maxConcurrency is good enough (128).

Now if order of the original query matter. concatMap is usually the operator that does the same thing as flatMap in order but sequentially, which turns out to be slow if the code need to wait for all sub-queries to be performed. The solution though is one step further with concatMapEager, this one will subscribe to observable in order, and buffer the results as needed.

Assuming retrofit clients are async or ran on a specific scheduler :

api1.items(queryParam)

.flatMap(itemList -> Observable.fromIterable(itemList)))

.concatMapEager(item -> api2.extendedInfo(item.id()))

.subscribe(...)

Or if the scheduler has to be set locally :

api1.items(queryParam)

.flatMap(itemList -> Observable.fromIterable(itemList)))

.concatMapEager(item -> api2.extendedInfo(item.id()).subscribeOn(Schedulers.io()))

.subscribe(...)

It is also possible to tune the concurrency in this operator.

Additionally if the Api is returning Flowable, it is possible to use .parallel that is still in beta at this time in RxJava 2.1.7. But then results are not in order and I don't know a way (yet?) to order them without sorting after.

api.items(queryParam) // Flowable

.parallel(10)

.runOn(Schedulers.io())

.map(item -> api2.extendedInfo(item.id()))

.sequential(); // Flowable