Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: response-cache different schema #2200

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

n1ru4l
Copy link
Collaborator

@n1ru4l n1ru4l commented Dec 4, 2022

I think the response-cache should be bound to the used schema. However, right now the response cache is shared between all possible schemas.

@changeset-bot
Copy link

changeset-bot bot commented Dec 4, 2022

⚠️ No Changeset found

Latest commit: 52d78b2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions
Copy link
Contributor

github-actions bot commented Dec 4, 2022

✅ Benchmark Results

     ✓ no_errors
     ✓ expected_result

     checks.........................: 100.00% ✓ 201502      ✗ 0     
     data_received..................: 28 MB   944 kB/s
     data_sent......................: 12 MB   386 kB/s
     http_req_blocked...............: avg=1.12µs   min=700ns   med=1µs      max=257.19µs p(90)=1.3µs   p(95)=1.6µs   
     http_req_connecting............: avg=1ns      min=0s      med=0s       max=109.19µs p(90)=0s      p(95)=0s      
   ✓ http_req_duration..............: avg=228.5µs  min=160.5µs med=206.1µs  max=18.26ms  p(90)=245.5µs p(95)=276.89µs
       { expected_response:true }...: avg=228.5µs  min=160.5µs med=206.1µs  max=18.26ms  p(90)=245.5µs p(95)=276.89µs
     http_req_failed................: 0.00%   ✓ 0           ✗ 100751
     http_req_receiving.............: avg=17.59µs  min=10.4µs  med=15.2µs   max=10.79ms  p(90)=20.2µs  p(95)=23.5µs  
     http_req_sending...............: avg=5.7µs    min=3.9µs   med=4.59µs   max=4.86ms   p(90)=6µs     p(95)=7.1µs   
     http_req_tls_handshaking.......: avg=0s       min=0s      med=0s       max=0s       p(90)=0s      p(95)=0s      
     http_req_waiting...............: avg=205.2µs  min=144.3µs med=186.3µs  max=18ms     p(90)=219.3µs p(95)=247.8µs 
     http_reqs......................: 100751  3358.237867/s
     iteration_duration.............: avg=293.14µs min=211.1µs med=264.59µs max=18.59ms  p(90)=316.3µs p(95)=353µs   
     iterations.....................: 100751  3358.237867/s
     vus............................: 1       min=1         max=1   
     vus_max........................: 1       min=1         max=1   

@github-actions
Copy link
Contributor

github-actions bot commented Dec 4, 2022

🚀 Website Preview

The latest changes to the website are available as preview in: https://ebeb39f0.graphql-yoga.pages.dev

@theguild-bot theguild-bot mentioned this pull request Apr 20, 2023
@EmrysMyrddin
Copy link
Collaborator

Do you have a real world example usage of this ? You mean a server that is swapping its schema dynamically ?

This was referenced May 7, 2024
This was referenced May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants