We recently migrated our simple SFDC ETL jobs to Boomi and noticed that for some reason the SFDC Get operations use a lot of CPU on the atom PC. The SFDC Get operation and the first Map right after the Get will use a full 1 CPU core on the atom machine which is unusual. We are running the atom on AWS VPC and it does not matter how many fields are returned by the SFDC SOQL in the Get operation (I have jobs with as little as 4 fields and some with 25+) the CPU usage is the same. I've also tried using batch results but that had no effect on CPU usage which drops to expected levels right after the first Map that converts SFDC data in to output DB profile. Did anyone experience this and knows what's causing this high CPU usage? I'm thinking that it has something to do with XML parsing of the SFDC result but interesting thing is that SFDC Send/update operations do not experience this issue.