HDD constantly writing data?

@mayer unfortunately not, if only it were that simple. I removed some unnecessary third party launch agents and launch daemons late last night, shut it down over night and it seems to be behaving slightly (maybe) better this morning, still writing data consistently when the laptop is running but it seems at a slower rate (still racking up MBs every few minutes). I guess a good question is if the "launchd" process should be writing any data at all, is that abnormal or normal? I have read a lot of people have issues with the "launchd" CPU usage but its normal for me, and others have this strange issue where it writes a lot of data. From what I gather the "launchd" process runs all the daemons so I have been trying to isolate where all the data is going, logs maybe?

Edit: definitely not logs as far as I can tell from both the /Library and /private log folders.

I could also be Spotlight indexing your contents.

@mayer I turned off spotlight yesterday because the mds_stores and mdworker processes were using a huge amount of CPU out of nowhere. I've been looking at the system logs looking for anything irregular,

"Mar 29 14:27:16 users-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit"

Does this mean anything? I am seeing it a lot in the system log. I'm going to try a safe boot start later and see if the problems persist to tell me if should just reinstall High Sierra

Edit: a little googling tells me a novice like me won't get anything from looking at the Console log and that line of code is normal. I am very befuddled, maybe I just never noticed this before I messed with it so I am being paranoid.

DirtyJetsamMemoryLimi means something is using up to much RAM

@mayer hmmm thats interesting as I just upgraded from 4 GB to 16 GB of RAM and activity monitor tells me I am only using 4 GB of memory with 3 GB of cached memory. Kernel_task is using about 950 MB of memory but everything else under 200 MB. I suppose putting the 4GB back in is another test I can do over the weekend along with a safe mode boot, though that seems unrelated to the HDD constantly writing data. It definitely seems to be affecting the "System" part of the storage as the "System" keeps getting larger. Its not affecting my computer speed but I am very curious as to what is going on, my only guess is that launchd is encountering an error and is stuck in a loop, but I cant find anything online along those lines of thinking.