Slow response times

Help
#1

Hello,

I’ve set up a very simple app where I can create and list rooms for bookings.

I have a test demo with 3 rooms in my collections.

Most of it, setup through a GraphQL schema upload.

It works great but I’m worried about response times I’ve been getting with very basic operations.

I have a allRooms query that returns a paginated set of rooms and I’m getting sometimes 4 sec request times. Seems like once it’s hot it gets faster and reached 800ms range but still that’s pretty darn slow.

Is it just what to expect with fauna, or is it because I’m using free tier?

1 Like
#2

@Christophe_Verbinnen welcome to the Fauna Forums.

It is not expected to see such high latencies. We have had some issues over the weekend which could have contributed to this. Can you please try again to see if you get same latencies ? Happy to troubleshoot more if you could share email id on the account.

#3

Hello Jay,

Thanks for your reply. It does seems like I’m not getting 4 secs anymore but still sometimes over 1 sec to return 3 items.

Screenshot from 2020-09-21 13-49-30
Screenshot from 2020-09-21 13-49-301484×193 32.8 KB

email is christophe[at]verbinnen.org

#4

Hi,

I’m in a situation that sounds very similar to Christophe’s. I have some straightforward, paginated graphQL resolvers that use simple indexes. Straight-up FQL based endpoints are not faster. I’m accessing the Fauna graphQL service via a Vercel serverless function that my Vercel-hosted frontend makes calls to. My email is “k at blwsk.com”.

As you can see below, response times average >1s, which is concerning to me as I validate Fauna for my use case.

Screen Shot 2020-09-21 at 5.36.45 PM
Screen Shot 2020-09-21 at 5.36.45 PM1428×572 87.8 KB

Thanks for your time.

#5

@Jay-Fauna did you ever get a chance to look into it?

#6

@Christophe_Verbinnen we have identified couple of places where these additional latency is coming from and will be working through the improvements in next couple of months. Till then, ~400ms to ~1s would be a norm on the GraphQL API side. This behaviour is not related to the size of collection.

On the drivers users can specify a timeout but that is yet to come on GraphQL API.

#7

Will this have an impact on FQL too?

#8

@skris GraphQL API internally calls FQL and one of the identified issue is the inconsistency in latencies on the FQL side. We are planning to fix this in next few months.

2 Likes
#9

Thank you @Jay for clearing this!