gosh, why is fetching data in app.prisma.io is THAT SLOW?

are you using demo server?

@huv1k yes

And define what is slow

Is there a way to use it for non-demo servers?

Demo servers has limits 🙂

ok then

You can host your server and connect cloud to it for example or use prisma serverless cloud

I see now 🙂

Yea, I know about limitations but I thought it was only for making requests from my server, not prisma's 🙂 Btw, what do you mean by 'use threads'?

I've been experiencing longer response times (5-15s) on demo-server recently, though no

throttled-by

headers are present, do you get these headers in your response?

We are right now in thread, but when you post this model and all mutations in general its just wall of text and its hard to navigate inside it

So you mean it is better to ask a question and add all this code inside the thread?

Yes exactly 🙂

Got it 🙂

@taikn hm there could be more things what are bad for example from are you making request etc i don't know what request and from where 😄 its hard to say something

Anyway, simple loading state will be ok for such things in app.prisma.io. Now it works even kinda ugly: you choose a model (an option in the 'Data Browser'), you see results, then you choose another model and you still see data from previous model but some fields are empty, lol, then all these fields disappear and shows up correct fields. It is so annoying, it is better to show just a loader instead of previous data

well I could just say that it was all fine probably until 1.22 beta got deployed or so

Ye, demo server are mostly for testing new stuff and trying stuff out. So they can be slower sometimes

I see