Yeah, there are several (cumulative) factors involved in the performance:death.crafter wrote: ↑August 25th, 2021, 3:56 pm Me who has kept the default 16 in my vis and still get decent perfomance
Actually it's about the Plugin used. I use Audio Analyzer. It gives decent performance over AudioLevel. Also, there is the fact that my vis is in whole one shape. So it doesn't eat much resources on redraw that's all.
- the plugin probably, as you said
- the size (possibly even type) of meters / skin and the measures complexity from a mathematical POV
- the resizing applied to meters like images
- the other CPU intensive operations in your system (including other skins AND external programs, not just Rainmeter)
- the update rate of each Rainmeter skin and its meters, not just the current one
- the number of AudioLevel parent measures, for visualizers (I, for example, have 2, one for Input and one for Output, since AudioLevel doesn't support dynamically switching the parent measure options like Port or ID)
- probably other factors as well
I know this because I constantly push Rainmeter to the limit and I'm very strict when it comes to performance / efficiency, LOL. That's why I just can't understand the idea of being ok with disregarding code optimization to improve performance, just because it's tolerable on higher end or own computers. That just feels wrong and a waste for me. If I can get an item for 5 bucks by choosing the right store nearby, I'm not gonna spend 50 on it even if I had millions - it's just plain common sense, not greed or avarice.