For reference, a 8 core + 16GB RAM configuration should be able to finish the pytorch compilation timely. The build takes roughly an hour. My observation is based on power9 -- on amd64 it should be something similar.
On Sun, 2023-01-29 at 11:09 +0800, Aron Xu wrote: > On Fri, Jan 27, 2023 at 9:42 PM Andreas Tille <ti...@debian.org> wrote: > > > > Am Fri, Jan 27, 2023 at 08:21:46PM +0800 schrieb Aron Xu: > > > On Fri, Jan 27, 2023 at 7:12 PM Andreas Tille <ti...@debian.org> wrote: > > > > make: *** [debian/rules:83: binary] Terminated > > > > ninja: build stopped: interrupted by user. > > > > > > > > could be a sign for this. Was I to naive to assume Salsa CI could > > > > manage a pytorch build and should we possibly switch this off again? > > > > > > > > > > Not sure but by wild guess it could be caused by running for too long? > > > > I do not think so. Since I was aware that it will take long I have > > adjusted the timeout from 1h (default) to 4h. The log stops a bit after > > 3h. To my experience if timeout is the reason the log ends with this > > information. > > > > Then I guess it could be out-of-memory, the build process is hungry > for RAM and a single cc1plus process can take at least up to 2GB > memory during my quick observation. > > Regards, > Aron >
