Further to my experience (problems) space-wise. The GUI itself must have a very negative impact on the size of the temporary plots. I set up 2 absolutely identical test machines. Same CPU's, same RAM, 2x 756GB ioDrive2 drives in Raid0, target storage a 1.92TB Intel SSD. With farming in Linux (Ubuntu Server 20.04) in CLI, I always can have 8 plots running in parallel with a specific setup. On the system plotting with GUI, I can be happy to get 6 parallel plots running. Otherwise, the md0 drive hits it's space limits quickly. I also note, in CLI mode, the max size of a temporary plot file, doesn't exceed 239GB. Temporary plot files generated on the system running the GUI, always hit 256GB.
Also, the same setup plotting through CLI only, generates a plot in 8 hours (2x E5 2630v3 with 2x ioDrives in Raid0). With the correct sequence and after a 12hour warm-up phase, I'm able to plot 24 plots every day (1 plot per hour). So with 3 machines, I'm able to generate 72 plots a day. Not much but .... Running the same plotting sequence with the GUI, leaves me with 12 hours per plot or 50% more. Of course, I exchanged hardware. Still the same.
So the (buggy) GUI adds to some curious 'ideas' ...