mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-17 20:41:49 +03:00
9a96e7d165
…rmance It makes sense to try to utilize multiple threads for metadata operations since we expect them to come one at a time (and likely at lower load periods anyway). As noted, although we build roles in parallel now, the admin role is still a bottleneck. For replace_metadata on huge_schema, on my machine I get: BEFORE: 22.7 sec AFTER: 13.5 sec PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3911 GitOrigin-RevId: 4d4ee6ac8b5506603e70e4fc666a3aacc054d493 |
||
---|---|---|
.. | ||
Cache | ||
Cache.hs | ||
Catalog.hs | ||
Diff.hs | ||
Enum.hs | ||
Function.hs | ||
LegacyCatalog.hs | ||
Rename.hs | ||
Source.hs | ||
Table.hs |