Setup of 100 Repetier-Servers

Marian

Hey, we are currently evaluating our options of how to handle our future print farm. For Repetier, the general idea would be the following:

Use one instance of Repetier-Server (on a desktop PC) which acts as a master. We would then upload all of our projects to this server.

Every printer got a raspberry pi running Repetier-Server. Each one would have the master server setup as an alternative server with access to the master servers projects. Projects do not get uploaded directly to each Pi's repetier server, they all access the master for that.

Questions:

1. When I start a print on any Printers Repetier-Server from one of the masters projects, will the master server "stream" the gcode file chunk by chunk or will the gcode be fully transferred to the printers Repetier Server before the print starts?

2. Will the master PC be able to handle 100 printer Repetier Servers simultaniously? (everything connected with ethernet)

Thank you!

Repetier

1. Prints only work from local print queue, so when you select a print in Project it gets copied, analysed and printed. So as soon as print starts master can die without issues.
2. This is no standby connecton so having 100 servers accessing the projects is no problem. Only during browsing and once per minute for reachability test is is queried. Also I have no 100 pis for testing I see no problem with that solution.

Marian

Alright, sounds good, thank you!

One follow up question to 1:

Is that copied file a temp file or would we have to erase content by time to time to prevent disk space getting used up?

Repetier

Printed files get deleted when to print counter is 0. Only if you abort it, it stays normally (see config settings) so you can reprint again without uploading. If you select to have no print queue in printer config it always gets deleted after print, but you loose all advanteges of the queue.