Reputation: 3838
I've launched a website today which makes heavy use of Starling and Workling to handle the background task queue.
Traffic has been heavy and although my server CPU/memory has not been under too much strain, the job queue is seriously backing up.
I am inexperienced with both Starling and Workling and urgently need to understand how I can speed up the queue.
This is probably quite a simple configuration issue but all suggestions and thoughts would be very appreciated.
Please let me know if you need more information.
Upvotes: 2
Views: 661
Reputation: 3838
I worked out how to do this in the end, it's very simple. Just start up more workling processes from the command line - there can be as many running as there is memory for. They will all pick up jobs from one or more instances of Starling, as specified in workling.yml. Note that :multiple
must be => true
in script/workling_client
for this to work.
Upvotes: 1
Reputation: 21467
If you have access to another server you can split the tasks up between the servers. You've probably seen it but Railscasts has a pretty good introduction to Starling and Workling.
There is also a book you can view on Google books with more advanced information:
Upvotes: 0