Is there a recommended size limit for Software Update Deployment Packages in SCCM 2012? I've read and heard that while there's no hard limit, it's recommended to build them and break them up by year, but some of the more recent years' packages are well over 12+ GB. Is there any performance drag or consequence to having those be so large? Should I break those large packages down in to smaller chunks?
I would like to just have one Deployment Package for simplicity's sake, but that would be monstrous. I guess, since those are just storing the update binaries and not doing much else, I'm not sure I understand if there is or why there would be a performance drag due to large sizes. Any suggestions or best practices for these?
Thanks,
Ryan