Can anyone from the Prisma team look at this pleas...
# prisma-whats-newh
harrisrobin
01/23/2018, 4:15 PMCan anyone from the Prisma team look at this please:
https://github.com/graphcool/graphql-server-example/issues/85
Would love an update as this is a pretty big blocker for me atm and can't show the project to a client as soon as i have custom resolvers
m
max
01/23/2018, 4:29 PMmore out of interest, are spaces linked to rating nodes? is your resolver carrying out a calc?
max
01/23/2018, 4:29 PMbascially what are you doing in your custom resolver?
h
harrisrobin
01/23/2018, 5:08 PM@max it's not just my custom resolver, the one in the boilerplate is very slow too (7 seconds).
Rating is related to a space. All I am doing is aggregating the count in one case and in the other case I am simply extracting the "perHour" out of the pricing object. I'm not doing anything complex, something is definitely wrong because if you just spin up the example you will encounter the same issue with the custom revolvers in the repo.
I feel this issue stems from Prisma itself rather than my resolver.
m
max
01/23/2018, 5:26 PMdo you think it's the computing power or the software?
max
01/23/2018, 5:27 PMnilan mentioned their are upgrading the architecture for the shared clusters
h
harrisrobin
01/23/2018, 6:40 PMI believe it's the computing power
harrisrobin
01/23/2018, 6:40 PMI'm hoping Prisma cloud will solve this