We observed (in T310093#8124847) that object validation code accounts for over 60% of function call latency.
Things to investigate:
- Can we get by with less validation?
- Can we make validation more efficient?
We observed (in T310093#8124847) that object validation code accounts for over 60% of function call latency.
Things to investigate:
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| Use heuristic type-checking instead of validation when resolving. | repos/abstract-wiki/wikifunctions/function-orchestrator!6 | jforrester | gerrit-823187 | main |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T315027 Reduce the performance cost of object validation | |||
| Open | None | T315026 Discuss Not Running Static Validation | |||
| Resolved | • maryyang | T315028 Consider Removing mutex/async from Schema | |||
| Resolved | • maryyang | T296841 Consider Locking Validators When `validateStatus` Is Called |
jforrester updated https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-orchestrator/-/merge_requests/6
Draft: Use heuristic type-checking instead of validation when resolving.
apine merged https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-orchestrator/-/merge_requests/6
Use heuristic type-checking instead of validation when resolving.