I have been testing the use of Pi zero W using a USB wifi adaptor and the CSI camera.
As it has been reported that this should solve the problem of excessive CPU usage by disabling the onboard wfi+bluetooth.
Setup:
Pi zero W
Pi camera connected via CSI
USB hub
USB wifi adaptor RTL8191SU chipset
Octopi (stretch)
With an active browser session, the webcam streaming, and a print from raspi SD card at 60mm/s I didn't see CPU usage above ~60% and usually sitting around 50%.
What are the concerns that I should be aware of that I would notice if the Pi zero was causing problems.
From what I have read people were seeing 80%+ CPU usage and freezing of the printer during a print resulting in poor prints or failed completely.
It is running well so far in my testing but they have only been 1hr test prints at 60mm/s. It shows about 30-35% CPU load without a camera stream running, octoprint task being the majority of that at around 20-25%. When streaming and viewing the stream, haproxy task adds 18-20%. The remainder tasks make up the difference. So I am usually showing peaks of like 55-60% total CPU usage printing and viewing the stream. Ill investigate further and try more situations i.e: loading a file while printing and viewing stream. So far no compromise in print quality from my baseline of a pi3b+.
It also works (okay) as a downstream rfc2217 receiver as streamed from a four-core Raspberry Pi 3B. And yet, a 3A+ downstream works even better in that role and has the correct connector size for the cable.
Gcode streaming directly from the Zero will end up costing you more failed parts over time. You've been lucky up to this point; the Zero has half the RAM and a single core. And jeez, you've got a webcam on that too. You'll eventually find some print job that will eat your face with plenty of short line segments.