I don't see any noticeable difference between 3 days and 15 days on CPU usage. It's a boatload of measures, but 90% of them are "child" WebParser measures, which use virtually no CPU. The relatively few "parent" measures do all the work.SilverAzide wrote: ↑June 17th, 2020, 6:15 pm LOL! Yes, agreed, as long as the days line up, it's all good!
To veer this thread slightly back toward the main topic... Should there be any concern with skins using this template about performance issues from having so many measures? The number of child measures is pretty ginormous now... something like 950, was it? It SEEMS okay, I've got 3 weather skins running all the time and Rainmeter is still using ~1.0% of my CPU, but I wasn't sure if there's any real benefit to cutting down the number of active measures (like organizing blocks of measures into groups, so if you only wanted a 5 day forecast instead of 15 days, you could turn off a group).
I did break it up already if you look at the current .rmskin. I have distinct includes for 3, 5, 7, 10, and 15 days. I didn't really do this for performance reasons, but just to make it easier to work with the skin in About/Skins.
I don't doubt that there is some small difference in the amount of resources used, nothing is entirely free. It's not going to be much, but I see no reason not to use the 5-day include if your skin is designed for 5 days.