I saw a few reports on Prima cloud demo servers in...
# orm-help
d
I saw a few reports on Prima cloud demo servers in EU being slow yesterday! If you are still facing slowness, please respond to this message as a thread.
Would love to collect more feedback and get this sorted .
t
I am still facing slow responses and timeouts, i wonder if its due limits, but i can't find any
throttled-by
headers attached to the response and then why was it earlier ok, is rate-limitation being introduced with recent beta?
d
Limitations for demo servers are documented here: https://www.prisma.io/docs/run-prisma-server/demo-servers-prisma-cloud-jfr3/#limitations If there is any other behavior like a timeout or slow response then we need to look into it, are you using the Europe region?
t
correct
πŸ‘ 1
Any other information from me that might help in getting this resolved/clarified?
@divyendu Any updates on this issue?
d
I will get back to you on this in a few hours.
πŸ™Œ 1
Have you considered using local prisma with docker till then? In place of the demo servers? πŸ™‚
t
I was thinking about it but I find the 'Data browser' on app.prisma.io pretty useful
And if its something that can be solved, i can wait
d
@taikn Did the performance increase for you in this context? We made some server upgrades a couple of days back. Also, we are working on a "secret" project called Prisma admin, that would bring data browser exque features and many more powers outside the cloud... please let me know your email in DM if you want an invite as soon as it is ready for preview 🐿️
u
Can i also ask for early access to prisma admin? I'm really looking forward to this technology, I don’t want to write an admin panel for a project πŸ˜‰
d
You are on my list, I will let you know as soon as it is ready πŸ™‚
☺️ 1
q
@divyendu I am still experiencing time-out issues. Seems to be related to nested queries.
Copy code
query items{
  allItems{
    id
  }
}
is fine. But doing:
Copy code
query items{
  allItems{
    id
    author{
      id
    }
  }
}
gives me
Copy code
"message": "The call to the group [username~serivce-name@dev] timed out.",
and returns null for author.
works fine in local docker setup
b
I am also getting timeouts, but on a loclally deployed instance of prisma. Are local deployments also rate limited?
d
No, local deployments are not rate limited, is there a lot of data in your local DB?