sillsdev / sillsdev/TheCombine
[DataEntry] Evaluate inconsistent time fetching frontier from backend
Open
@jasonleenaylor is already working on this.
Since Oct 24, 2023.
performance
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 10
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 9
Description
In a project on QA (v1.1.3-master.23) with the Natqgu.zip lift imported, in Google Chrome (118.0.5993.89) on Windows 11 Pro (22H2, x64, i7-1355U CPU, 32 GB RAM), in Data Entry, 10 consecutive fetches of the frontier took:
- frontier | 1.3 MB | 1.82 s
- frontier | 1.3 MB | 1.63 s
- frontier | 1.3 MB | 1.69 s
- frontier | 1.3 MB | 2.14 s
- frontier | 1.3 MB | 1.93 s
- frontier | 1.3 MB | 1.98 s
- frontier | 1.3 MB | 1.73 s
- frontier | 1.3 MB | 1.79 s
- frontier | 1.3 MB | 1.78 s
- frontier | 1.3 MB | 1.79 s
The range from 1.63 to 2.14 is a bit surprising.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.