Questions about Latency Measurement
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3k
- Forks
- 234
- PR merge metrics
- No merged PRs in 30d
Description
Thank you for sharing this impressive work! I’m particularly interested in the claim: "Optimized for speed: Achieves 60ms latency per image (A100 or RTX3090, FP16, ViT-L)." Could you please clarify the following details?
Latency Measurement Method: How did you measure the 60ms latency per image? For example, did you use Python’s time.time() for timing, or did you rely on tools like torch.profiler or CUDA events (torch.cuda.Event) for more precise GPU timing?
Input Image Size: What was the input image resolution used to achieve the 60ms latency result? For instance, was it a standard size like 224x224, 384x384, or something else?
These details would help me better understand the performance characteristics of your implementation. Thanks in advance for your time and insights!
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.
Research direction
No files, tests, or entry points are named. Start by locating the source of the 60ms performance claim; done means documenting the timing method and input image resolution used for that result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision, performance
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100