From: Yasuaki Kudo <yasu@yasuaki.com>
To: help-guix <help-guix@gnu.org>
Subject: Guix for Corporate "Batch Jobs"?
Date: Wed, 9 Mar 2022 06:16:41 +0900 [thread overview]
Message-ID: <506EEA75-0A98-4F04-9BC2-C7588FF9A65C@yasuaki.com> (raw)
Hi,
In many so-called Application Support jobs in the enterprises, one of the core responsibilities is to see through the daily completion of "batch jobs" - those I/O heavy processes that take a long time to run, even with parallel processing.
And at the core of it is to "re-run" the jobs, after due troubleshooting.
In many workplaces I have seen, teams ended up writing their own job schedulers based on cron or used proprietary software such as Autosys (and in Japan, there are local brews such as A-Auto, if I remember the name correctly).
But none of the solutions above take good care of the mechanical incremental computation aspect and a lot of optimization (say skip this and that because they don't matter during re-runs) depend on the operators' sweat and judgement 😅
Can Guix be put into good use in this area do you think? Or maybe another way of asking this question is, can Guix be used a general compiler such as 'make'? Knowing that 'make' still exists so - is there any reason why Guix just can't take over?
Maybe similar questions have been already asked in the Nix world as well? I would love to know! 😄
-Yasu
next reply other threads:[~2022-03-08 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 21:16 Yasuaki Kudo [this message]
2022-03-08 23:18 ` Guix for Corporate "Batch Jobs"? Phil
2022-03-09 8:20 ` Ricardo Wurmus
2022-03-09 8:49 ` Yasuaki Kudo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=506EEA75-0A98-4F04-9BC2-C7588FF9A65C@yasuaki.com \
--to=yasu@yasuaki.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).