Reviews about Async processing gem called Sucker Punch

81 views
Skip to first unread message

Harisankar P S

unread,
Mar 19, 2014, 7:00:19 PM3/19/14
to kerala-ruby-users-group
Hi guys,

I am working in an application where I have a requirement to send a newsletters to all the members of the application. To make sure the application doesn't become non responsive when the email is being send, I decided to use some background processing to speed things up. I have experience using Delayed Job and Resque. But last week i came across this gem called Sucker Punch[1]. The advantage regarding this gem is that the background processing would be done asynchronously in a single process.


Has anyone used this gem in production? How was your experience?



Cheers,

--

mukesh.eledath

unread,
Sep 1, 2014, 6:30:56 AM9/1/14
to kerala-ruby...@googlegroups.com
Hi Hari,

This is so late to reply, but I was looking for a google group for discussions on sucker_punch and saw your post. I just set the newsletters for one of our websites with sucker punch and its working well until now. I was using sidekiq, but its very heavy and crashes often. Also, we had an issue of email flooding when the server restarted, as the email queue was not purged. Pls share your reviews and suggestions on using sucker_punch, if you have used it.

Regards,

Harisankar P S

unread,
Sep 1, 2014, 7:47:13 AM9/1/14
to kerala-ruby-users-group
Hi mukesh,

Ya i have used the gem, quite helpful and simple if your load is minimum and if your main server can handle the extra load. 

Pros:
The thing i liked about sucker punch is its simplicity of integration, and didn't cause much problem for me.

Cons:
When the email count reached 10,000 emails per day itself, the main rails app started to take the toll. Our server was an ec2 micro.
Finally i moved back to sidekiq, as i was able to run the worker on another server (another ec2-micro). 

My verdict is:
Sucker Punch is good to get started, really simple, light and clean. But once the load increases you should consider moving back to sidekiq.

PS: Regarding the queue not purging i had the same problem. I wrote a rake task to run these three commands

Sidekiq::Queue.new("infinity").clear
Sidekiq::RetrySet.new.clear

​and add it to my capistrano deploy file.​ 

cheers,



--
You received this message because you are subscribed to the Google Groups "Kerala Ruby Users Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kerala-ruby-users...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

Mukesh Unnikrishnan

unread,
Sep 1, 2014, 9:07:03 AM9/1/14
to kerala-ruby...@googlegroups.com
Dear Hari,

Thanks a lot for your suggestions. We are far to go to 10000 emails/day now. So sucker punch is better, and thanks for your remark on sidekiq queue purging problem. Will try it.


Regards,
Mukesh. E
RoR developer
FOSS enthusiast
Reply all
Reply to author
Forward
0 new messages