mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-14 08:02:15 +03:00
ci: tag release v2.8.3
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4915 Co-authored-by: Divi <32202683+imperfect-fourth@users.noreply.github.com> Co-authored-by: Rikin Kachhia <54616969+rikinsk@users.noreply.github.com> GitOrigin-RevId: e7f5372829b8bb4d84f30b20c4cd488f516389d1
This commit is contained in:
parent
ffad733bd3
commit
b4f9626b00
22
CHANGELOG.md
22
CHANGELOG.md
@ -53,6 +53,28 @@
|
||||
- console: Hide TimescaleDB internal schema from data tab
|
||||
- console: support naming convention in source customization for postgres DB [CON-297]
|
||||
|
||||
## v2.8.3
|
||||
|
||||
### Bug fixes and improvements
|
||||
|
||||
- cli: fix performance regression with large metadata in `metadata apply`
|
||||
|
||||
During the execution of `metadata apply` command, the YAML metadata is
|
||||
converted into JSON format because the server API accepts metadata in JSON
|
||||
format. For large metadata(> ~20k LOC), due to a recent change this conversion was
|
||||
taking upwards of 2 minutes of time, increasing exponentially with metadata size.
|
||||
With the changes in this release, the performance regression has been fixed.
|
||||
Following is a benchmark comparison of time taken for YAML to JSON conversion
|
||||
before and after the changes for different metadata sizes:
|
||||
| Metadata size(LOC) | Before(seconds) | After(seconds) |
|
||||
|--------------------|-----------------|----------------|
|
||||
| 10k | 8.7 | 0.22 |
|
||||
| 20k | 15.9 | 0.29 |
|
||||
| 50k | 89.5 | 0.52 |
|
||||
| 100k | 271.9 | 0.81 |
|
||||
| 300k | - | 2.3 |
|
||||
|
||||
|
||||
## v2.8.2
|
||||
|
||||
### Bug fixes and improvements
|
||||
|
@ -91,3 +91,4 @@ v2.8.0 47
|
||||
v2.9.0-beta.1 47
|
||||
v2.8.1 47
|
||||
v2.8.2 47
|
||||
v2.8.3 47
|
||||
|
Loading…
Reference in New Issue
Block a user