Heap memory is a scarce shared resource. Those names must be stored there. If average length is say 24 characters, there is an 8 byte overhead per heap allocation, so 32 bytes per x 60 = 1,920 for the names alone. That’s about 10% of typical available heap. Overall, each of those measurements is probably closer to 80 bytes so roughly 25% of available heap. Now you need large buffers to send that data, so not a good situation.
It’s not like this data isn’t available. You can get it direct from the IoTaWatt if you need to know.
IoTaWatt stores cumulative Wh and cumulative VAh for each input. Additionally, it uses the reference to the appropriate voltage channel and the cumulative measurement hours associated with each measurement interval. All of the metrics are derived from that.
As I said, kWh = Wh / 1000, so saving both is redundant. You can integrate Watts in influx Query to get Wh. Same goes for integrating VAR to get VARh. VAR is relatively new and is really only useful for billing in commercial tariffs.
I only upload Watts and Voltage.