I just checked and CPU went from ~15% to ~35% on i5 4590.
WG++ is very resource hungry and the grabbing for schedules direct is poorly written in my opinion.
Thanks for the quick response, saarg! I'm running an old Sempron 145 (2.8GHz) so I guess that is to be expected, then. I have to agree with your comment about it being poorly written, based on my experience with the same hardware and mc2xml. Thanks again!
FYI for US Schedules Direct users:
I set up an ubuntu 14.04 docker with XMLTV and it works as it should. I can now grab 14 days of data for 16 channels in about 25 seconds (6MB file). My old CPU still spikes to 100%, but only for 20 seconds instead of 10 hours.
I thought this might be of interest to those that are in a similar boat. I'll put together an unraid template for it as an alternative for those in the same boat. WG++ seems awesome, but just not for Schedules Direct users.