Search API Delayed Results vs Users API

There seems to be a substantial delay in the Search API vs the Users API when querying the same data, in the case that I've found, the tickets that are assigned to a specific user.

For example, if I create a new ticket in the system, assign it to a user and use the User API to request tickets assigned to that user with the following query:

users/(some user id)/tickets/assigned?sort_by=updated_at&sort_order=desc

I will immediately see the new ticket that I just created in the API response, which is exactly what I expect to happen.

However, if I use the Search API to request the tickets assigned to a user using the following query:

search.json?include=tickets(users)&query=type:ticket,status:open,sort:updated,order_by:desc,assignee:(some user id)

There will be a significant delay in between when I created the new ticket, and when I actually see it in the Search API response.  In my experience it takes several minutes to finally be returned in the response.

I've found that the Search API is very useful for combining datasets and simplifies complex API requests, however the delay mentioned above is an issue for our application.

My questions are:

• Is this expected API behavior / is it a known issue?

• If so, can we expect any updates in the near term that will remove or reduce this delay?

• Since obtaining the most recent tickets assigned to a user may require multiple API calls (with the method above). Are there any other alternative or suggested solutions for obtaining the most up-to-date tickets assigned to a user without a significant delay? Using a single API request is preferable.