hi! I have the following query:

query Test {
  business(where: { id: "93f13" }) {
    publicationBatches {
      publications(first: 1) {
        id
        localeCode
        paged {
          id
          pages {
            pageNumber
            image {
              url(width: 700)
            }
          }
        }
      }
    }
  }
}

what essentially happens is: 1) fetch business 2) fetch publication batches (there's 3) 3) fetch publications for publication batches (there's 1 for each) 4) fetch pages for each publication (there's around 100 for each) 5) fetch image for each page that's at least 600 objects that need to be fetched and it takes 5-10s with the above query. I was under the impression that Prisma had an efficient dataloader but I can't launch with these response times. what can I do to improve loading times?

What is the size of the response? Can you please check in chrome network tab how much time of the 5-6s is actually to move the data over the network?

Thanks! A few more questions. 1. Is this request on your application server or Prisma directly? 2. How much data do you have in the database?

this is locally using Docker using the Playground on localhost. I don't really have any data. maybe around 5000 objects

Is this also slow locally? Can you please share a minimal reproduction as an issue then? with some sample (maybe fake) data? https://github.com/prisma/prisma/issues/new?template=bug_report.md

I've only tested it locally, which is where it's slow

Sure, a reproduction with similar amount of data / data structure would be great. Too many moving parts otherwise like the application server etc!

will do. there might be an issue with Docker or something like that. because it just took 70 s to run

prisma deploy

after making a small change

Could be!

thx for your help

Awesome, thanks for notifying 🙂