You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for open-sourcing your work with the greater community. The recovered high-frequency details are indeed noticeable, albeit with extra training latency. One other issue I'd like to highlight, and hopefully get your input on is the GPU memory overhead which seems to scale rather intensely with image resolution and number.
Is there a way to mitigate this memory overhead for larger datasets without trading off too much of accuracy? The rays/batch size does not seem to help in this regard.
The text was updated successfully, but these errors were encountered:
Thanks for open-sourcing your work with the greater community. The recovered high-frequency details are indeed noticeable, albeit with extra training latency. One other issue I'd like to highlight, and hopefully get your input on is the GPU memory overhead which seems to scale rather intensely with image resolution and number.
Is there a way to mitigate this memory overhead for larger datasets without trading off too much of accuracy? The rays/batch size does not seem to help in this regard.
The text was updated successfully, but these errors were encountered: