4 ms·
We tried to use this in our last project and ended up writing the mother ship and workers from scratch because there didn't seem to be a community behind gearma
by enigmabomb 15y ago
We tried to use this in our last project and ended up writing the mother ship and workers from scratch because there didn't seem to be a community behind gearman. As soon as the nda runs out, I'm going to open source it as a competing framework.
- rubashov 15y agoWhat was your problem with it? I have tried to use Condor for a couple things recently and was annoyed enough by it I concluded Gearman was probably the better approach, though I haven't used Gearman. For the record, Condor probably works fine for its primary use case, which is long running single threaded processes on Unix that eat an input file and spit out an output file before terminating. I was trying to use it to have a bunch of processes on Windows that also occasionally write to a database. Was also trying to tag "slots" on specific machines to use certain installed dependencies. I advise against trying to use Condor and Windows, or on trying to use any of its advertised advanced features beyond the basic "standard" or "universe" model. Have had no end of trouble with the "stored credentials" feature that lets you run a process under a specific account.
- mst 15y agoI think a part of the problem there may be that a substantial percentage of the original user community are perl hackers, and tend to discuss their Gearman usage in the context of whatever else they're using - I see Gearman discussions reasonably often on the Catalyst IRC channel, for example. Another reason is quite possibly that for the vast majority of tasks, Gearman "just works" - if the obvious way to use a piece of software works first time, talking to other users isn't particularly necessary (there's not really a GNU cat community either, for example :) I'm not entirely sure what you'd do to fix that though (or even if there's anything except perception to be fixed)