Someone else with a low vram card (<6GB) whose generation times are much worse since today's updates? #1166
-
Since I made the updates today (Aug 15th) I have noticed a massive deterioration in performance (from +-25 s/it to +-37 s/it) and would like to hear your experiences to know if it is due to my hardware / other external circumstances or due to the latest updates. |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments 16 replies
-
One thing I noticed is that the program now only uses 93.4% of the VRAM instead of 100% |
Beta Was this translation helpful? Give feedback.
-
same here |
Beta Was this translation helpful? Give feedback.
-
Same here, Tesla P40 went from 7.14 it/s to like 16-32. |
Beta Was this translation helpful? Give feedback.
-
If someone here knows how to git checkout, put full console logs before after some commit with different speed. Sometimes when I find things slower, it often turns out to be caused by different model - note that nf4, nf4v2, q4 are expected to have speed difference. these days people change models a lot and one may forget they changed models |
Beta Was this translation helpful? Give feedback.
-
version: f2.0.1v1.10.1-previous-356-g8eeeace7 here is my info, it starts with 5s/it which is great improvement over the past commits, but it keep accumulating until it reach 40s/it at the end, i use --all-in-fp32 --xformers on Tesla p40 24gb card |
Beta Was this translation helpful? Give feedback.
-
Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug 1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)] It previously set the vram status to LOW-RAM, which I think is more suitable for my poor video card,^_^ |
Beta Was this translation helpful? Give feedback.
-
UPDATE: Based on suggestions from #1370 I was able to use the latest version Commit hash: 49435de at old top speeds, where it was before ~ Aug 5th
For Pascal, issues seem to start even earlier, at least for me. Switched back and forth between commits to find where my speed issues started, used absolutereality_v181.safetensors as an example model. For me it is a difference of ~13s vs 95s, same settings, seeds etc. yield same images, so things seem to be ok on the settings side. -> ~before Aug. 5th performance is great Python 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:38:17) [MSC v.1929 64 bit (AMD64)] (plz refer to the commit hash above - in screenshot it is a local commit, where I stored browser startup settings in the webui-user.bat, no relevance for results) Python 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:38:17) [MSC v.1929 64 bit (AMD64)] |
Beta Was this translation helpful? Give feedback.
-
Hey everyone, I merged many of your feedbacks to main, please update, and remove all setting/cmd flags, change back to default settings, and test the performance again. it can be helpful if you can put test statistics here (after updates) see also 31bed67 |
Beta Was this translation helpful? Give feedback.
-
Performance has improved massively thanks to your updates and is now back to the level it was at before the degradation. Thank you! |
Beta Was this translation helpful? Give feedback.
-
Performance is better now but I have one notice, the s/t is accumulating. |
Beta Was this translation helpful? Give feedback.
Hey everyone, I merged many of your feedbacks to main, please update, and remove all setting/cmd flags, change back to default settings, and test the performance again.
it can be helpful if you can put test statistics here (after updates)
see also 31bed67