search

lyonrb / wishlist

Meetup talks scheduler
https://github.com/lyonrb/wishlist/issues
7 stars 0 forks source link

Sidekiq #10

Closed michaelbaudino closed 10 years ago

michaelbaudino commented 10 years ago

I'd love to hear a presentation and/or feedback about Sidekiq.

Has anyone any experience with it ?

tigrish commented 10 years ago

:+1: especially as a performance comparison with Resque - specifically I'm thinking about dyno costs on Heroku.

dmathieu commented 10 years ago

I don't have enough material to do a presentation for now. But you might be interested in this Experiment with Sidekiq, Ruby and Go.

michaelbaudino commented 10 years ago

Neat post, thanks. You may have enough material to do a presentation by October meetup ;-)

michaelbaudino commented 10 years ago

@neophiliac you offered to try to setup a remote talk by Sidekiq creator. Is this still on ? Would December or January meetup be a wise target ?

neophiliac commented 10 years ago

I misunderstood him; he doesn't have time. But he said he will support me if I prepare a talk on Sidekiq. So I will prepare a talk for the December meeting.

michaelbaudino commented 10 years ago

Nice :-)

neophiliac commented 10 years ago

Regarding the dyno comparison, Mike says in his 2012 talk ( https://www.youtube.com/watch?v=RwUHcBg0i7Q ) that one Sidekiq user went from 160 dynos with Resque to 10 with Sidekiq. I think it depends on what your workers are doing though. For I/O-bound work (like sending email) this is probably a representative ratio.

Are there other questions I should try to address? My first thought is to take a template app that sends email to users after registration and make it send asynchronously. I also want to do some other work asynchronously.

tigrish commented 10 years ago

I'd love to hear about scheduling and locking which require additional plugins in Resque.

pilap82 commented 10 years ago

Maybe that's too specific but talking about automatic scaling would be nice (typically useful on Heroku).

Also there seems to be something tricky about jobs that can be run more than once… Could be worth mentioning this too? :)

Le 14 oct. 2013 à 12:48, Kurt Sussman notifications@github.com a écrit :

Regarding the dyno comparison, Mike says in his 2012 talk ( https://www.youtube.com/watch?v=RwUHcBg0i7Q ) that one Sidekiq user went from 160 dynos with Resque to 10 with Sidekiq. I think it depends on what your workers are doing though. For I/O-bound work (like sending email) this is probably a representative ratio.

Are there other questions I should try to address? My first thought is to take a template app that sends email to users after registration and make it send asynchronously. I also want to do some other work asynchronously.

— Reply to this email directly or view it on GitHub.

neophiliac commented 10 years ago

OK, I am preparing some code to demonstrate Sidekiq for sending email. I will include tests. Registering on the site will send a confirmation email and also schedule a followup email. I will show some worker code that is not idempotent, and refactor it so it is. I will look into locking. Autoscaling may be too much for a short talk, sorry.

It sounds like December is full, so I'll plan on January.

dmathieu commented 10 years ago

@neophiliac: welcome into the @lyonrb organization :sparkles: I just assigned you to this issue.

dmathieu commented 10 years ago

@neophiliac: this issue was in the january milestone. Though we forgot you, sorry :confused: Would you be up to talking about it in february?

neophiliac commented 10 years ago

Yes. I have a little more code to write, and Mike Perham has agreed to review my work before I present it. I will be ready for the next meeting.

dmathieu commented 10 years ago

Awesome! I'm scheduling you :smile:

cappert commented 10 years ago

hi @neophiliac, I know the meetup is still 2 weeks away, but do you know if you'll be able to make it ?

neophiliac commented 10 years ago

Oui, bien sûr!

michaelbaudino commented 10 years ago

:+1: