Extremely slow rendering speed when preparing dataset for TRELLIS training set.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13.7k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Thank you for your great work and open-sourced training codes.
However, I found that when preparing ABO dataset as my training data, the rendering speed is extremely slow. Like 500 seconds per iteration. Like shown below.
I am wondering if this is common or not. Since it takes too much time indeed.
Thank you!
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 with the ABO dataset preparation and rendering entry points in the TRELLIS training code, then reproduce the reported 500-second iteration time. Compare the observed timing with the expected workflow and inspect the rendering stage to determine whether the slowdown is expected or indicates a defect. Done means the cause is documented or the rendering performance issue is resolved and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-graphics, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100