On Tue, Nov 4, 2008 at 8:00 PM, Justin Lynn <[EMAIL PROTECTED]> wrote: > > Jacob Atzen wrote: >> Hi all, >> >> I'm running a private gitorious server. Right now the creation and >> cloning of repositories takes a while as the task performer script is >> being run by a cron job once a minute. Anyone got some ideas how to >> make it not have to wait for cron. I though about daemonizing the >> task_performer script, but before I go that route I wanted to hear >> what you guys are doing. >> >> -- >> Thanks, >> - Jacob Atzen > Something like a worker process for workling might do the trick if me > move to starling for the message queue. It could really help gitorious > scale out nicely or at least better than the current cron system does.
Yeah, I've been looking into some other queuing systems, my only requirements are that I can add many workers (without race conditions) and (maybe) that it's persistent. Here's the pickle though; on my client projects I'm all for dividing a logical application up into many smaller pieces/apps, but I'm thinking gitorious might have to strike a balance between being able to be installable easy on behind-firewall setups and being architected good enough to function on gitorious.org. So far I think that can be done, but there may be a place in the future where those two have to be divided. But not quite yet… > > J Cheers, JS --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Gitorious" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gitorious?hl=en -~----------~----~----~----~------~----~------~--~---
