XYZ is a verbose, uncompressed ascii format so you should anticipate large files. However, you have quoted your area as -a_ullr -89.2972 60.0378 -117.719 44.901. I'd have expected GDAL to give you an error message for those numbers since -117 is further west than -89 meaning you've actually quoted URLL and not ULLR. Perhaps because you are in WGS84, GDAL is content to go 'the long way round' the globe. I notice your prime meridian is Greenwich so perhaps you meant: -a_ullr -117.719 60.0378 -89.2972 44.901. This will give you an area of 26.52 x 15.13 degrees (instead of about 333.48 X 15.13! which would indeed be a massive file in xyz).

Even the area you intend in XYZ is going to be a big file especially with 15 decimal places for your X and Y values and int32 for your z values (though I'd not expect quite as much as 100GB+). Do you really need to use XYZ?

XYZ is a verbose, uncompressed ascii format so you should anticipate large files. However, you have quoted your area as -a_ullr -89.2972 60.0378 -117.719 44.901. I'd have expected GDAL to give you an error message for those numbers since -117 is further west than -89 meaning you've actually quoted URLL and not ULLR. Perhaps because you are in WGS84, GDAL is content to go 'the long way round' the globe. I notice your prime meridian is Greenwich so perhaps you meant: -projwin -117.719 60.0378 -89.2972 44.901. This will give you an area of 26.52 x 15.13 degrees (instead of about 333.48 X 15.13! which would indeed be a massive file in xyz). Use -projwin to clip a subwindow. The -a_ullr parameter assigns new dimensions to your output but does not clip (so you may still expect a large file if you use that instead of projwin). For more information see the documentation here.

Even the area you intend in XYZ is going to be a big file especially with 15 decimal places for your X and Y values and int32 for your z values (though I'd not expect quite as much as 100GB+). Do you really need to use XYZ?