microsoft / microsoft/OmniParser
Start gradio_demo.py Very slow
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 25.4k
- Forks
- 2.2k
- PR merge metrics
- No merged PRs in 30d
Description
I have downloaded weights locally and enabled GPU,
At the same time, change to demo.launch in gradio_demo. py (share=False, serverless=7861, serverless=0.0.0.0 ')
Starting the gradio_demo script is very, very slow, and may take several minutes or even longer. I don't know why (disconnecting from public network connection)
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
Start by reading and running gradio_demo.py, focusing on the demo.launch configuration and the local-weights, GPU, and network conditions described in the report. Compare startup behavior with and without public network access, then document the cause and verify that startup completes without the reported multi-minute delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100