incremental: remove filtering from rewrite - #4032
Conversation
|
Hi @yaacovCR, I'm @github-actions bot happy to help you with this PR 👋 Supported commandsPlease post this commands in separate comments and only one per comment:
|
✅ Deploy Preview for compassionate-pike-271cb3 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This comment has been minimized.
This comment has been minimized.
@yaacovCR The latest changes of this PR are available on NPM as Also you can depend on latest version built from this PR: |
|
Looks like this PR is about 5-10% slower than #4026 using the supermassive benchmark from #4008. As usual, the results are pretty noisy, what I am most interested in is the run for already parsed queries, and the noise seems low enough to get a comparison. So @robrichard, the question is whether we can optimize this further and make up that ground and whether the 5-10% differential is worth the divergence from the spec edits. This PR: yaaco@Yaacov-15 MINGW64 ~/Documents/GitHub/graphitation/packages/supermassive (main) yaaco@Yaacov-15 MINGW64 ~/Documents/GitHub/graphitation/packages/supermassive (main) yaaco@Yaacov-15 MINGW64 ~/Documents/GitHub/graphitation/packages/supermassive (main) yaaco@Yaacov-15 MINGW64 ~/Documents/GitHub/graphitation/packages/supermassive (main) With #4026: yaaco@Yaacov-15 MINGW64 ~/Documents/GitHub/graphitation/packages/supermassive (main) yaaco@Yaacov-15 MINGW64 ~/Documents/GitHub/graphitation/packages/supermassive (main) yaaco@Yaacov-15 MINGW64 ~/Documents/GitHub/graphitation/packages/supermassive (main) yaaco@Yaacov-15 MINGW64 ~/Documents/GitHub/graphitation/packages/supermassive (main) |
This comment has been minimized.
This comment has been minimized.
@yaacovCR The latest changes of this PR are available on NPM as Also you can depend on latest version built from this PR: |
5fe0b2f to
f2ec6a0
Compare
|
take-two = #4026 |
bff8561 to
ba7770a
Compare
ba7770a to
a043386
Compare
|
I've actually gotten some better results with this, so I am going to fold this into #4026. We can always re-introduce filtering again if need be, but it would be nice if the implementation could match the spec. |

depends on #4026
removed filtering again