Sidekiq for Crystal | Mike Perham
2016-05-25 Sidekiq is a popular job framework for Ruby. Now we’re bringing it to Crystal! Why Crystal? I wanted to use a language that was a good complement to Ruby. Its syntax is similar enough to Ruby that I can reuse a lot of code but it adds a huge leap in performance. In summary: very similiar syntax to Ruby at least 3-5x faster than Ruby 2.3 on most code at least 3x smaller in memory footpri
Taming Rails memory bloat | Mike Perham
2018-04-25 MRI, the standard Ruby interpreter, has a serious problem with memory bloat in large Rails apps. It’s quite common for me to see Sidekiq processes which are 1-2GB in RSS or even larger! It turns out that a large part of this memory usage is due to memory fragmentation: MRI uses the OS’s memory allocator by default (on Linux, almost always GNU glibc), which seems to work poorly with Ruby
Ruby Optimization with One Magic Comment | Mike Perham
2018-02-28 Software performance optimization is simple: find a way to do less. Ruby has a reputation for being slow and, while that impression is a decade out of date, one of the leading offenders has been the garbage collector. This leads to the question: can we speed up Ruby by creating less garbage? Absolutely! A String Primer Ruby has an unfortunate default semantic that all Strings are mutabl
Happy 6th Birthday, Sidekiq | Mike Perham
Six years ago I shipped Sidekiq v0.5.0 and changed my life. I talked to some developers recently: “I had been working in Go for a while but I kept coming back to Ruby because Sidekiq makes everything so fast and easy to scale.” This is my recipe for success. Sell a product developers want because it makes their job so much easier. You don’t need a sales force when developers evangelize your produc
Faktory 0.7.0 Released | Mike Perham
2018-01-08 Faktory is my brand-new background job system for every programming language. If you want to learn more, see the intro. It’s been three months since the initial launch in October and I’ve heard of several successful rollouts to production. If you were reluctant to try out Faktory before, it’s time to start looking into it because the biggest release of Faktory yet is now available to al
Sidekiq Pro Statsd support -- new and improved!
Several customers have been asking for more metrics to track Sidekiq internals: when is a job dropped due to uniqueness or expiration? I've had to put off the work while working on Faktory but recently I took a week off to focus on Sidekiq and implement this feature. New and Improved Sidekiq Pro 3.6 has a brand new Statsd metrics subsystem. Statsd is a de facto universal standard for metrics in op
Getting Started with Faktory | Mike Perham
2017-11-13 When I unveiled my new background job system Faktory three weeks ago, I didn’t have an easy path for people to install and try Faktory themselves. Now there is; let’s get it running! Homebrew If you are running macOS, it’s installable with Homebrew: > brew tap contribsys/faktory > brew install faktory ...two minutes pass... > faktory Now open your browser to http://localhost:7420 Docker
Introducing Faktory | Mike Perham
2017-10-24 Yesterday I explained how a good background job framework is critical to scaling business applications. Today, meet Faktory. I’ve spent the last six months building Faktory, a new background job system which aims to bring the best practices developed over the last five years in Sidekiq to every programming language. The Basics Faktory is a server daemon which provides a simple API to pr
The Future of Background Jobs | Mike Perham
2017-10-23 Whether sending an email, adding an item to your cart or tracking an impression, modern businesses can be modeled as a series of business transactions. I believe that a good background job framework is the best way to execute these transactions and scale your business applications across many machines. A good background job framework gives you: a simple API for defining and calling jobs
Retries and Exceptions | Mike Perham
2017-09-29 Do you hate getting your inbox filled with errors you know you can ignore? Here’s one cool trick to make them disappear. If you are writing a background job, it is best practice to have that job retry in the case of unexpected errors. Networks can be flaky, code can be buggy, data can be sketchy – as they say, “stuff happens”. Sidekiq’s default policy for jobs and retries is simple: if
Hello Sidekiq 5.0 | Mike Perham
2017-04-25 After a few months of work, I’m happy to announce that Sidekiq 5.0 is now available. Sidekiq 5.0 refactors the core job processor to work better with Rails 5 and includes a few breaking changes that have been pending for a while. What’s New? Rails 5 native! Sidekiq::Processor has been redesigned to work well with Rails 5.0’s Executor. The Executor is a new API which needs to wrap any us
Monitoring Redis | Mike Perham
2017-04-20 Redis is widely used by the Ruby community but, like any complex piece of infrastructure, isn’t well understood by many of its users. I wanted to write a blog post that would answer the question: How can I check on the health of my Redis server? Here’s a few things you can do to better understand your Redis server. Ask for Info The info command is the easiest way to get an overall view
Five Years | Mike Perham
2016 Year in Review Sidekiq Rails 5.0 support Dropped Sinatra dependency 16 bug fix releases Sidekiq Pro timed_fetch and super_fetch algorithms 17 bug fix releases Sidekiq Enterprise Job data encryption Multi-Process with memory monitoring Web UI authorization You Want Five? Sidekiq 5.0 beta is now ready for testing in non-production environments. The internals have been redesigned to work better
How to Charge for your Open Source | Mike Perham
2015-11-23 Every month or so we hear of another high profile open source developer who flips the table and rages about open source because of burnout, most recently Ian Cordasco and Ryan Bigg. Does this sound familiar? Spend many hours writing software. Spend many hours supporting users and solving their problems. Make $0. If you were a freelancer and did that with clients, you’d be: Overwhelmed w
Memory-hungry Ruby daemons
2009-05-25 We’ve had a perplexing issue with our Ruby daemons at OneSpot: they seem to grow to 300-400MB each within about 30 minutes, at which point our Monit scripts restart them. We suspected a memory leak and so upgraded from stock Ruby 1.8.5 shipped with CentOS to the latest REE 1.8.6 but nothing changed. I also saw a very similar issue at FiveRuns. Why is this problem seemingly endemic, even
RubyConf 2008: The Aftermath | Mike Perham
2008-11-09 I got back to Austin last night after a great three days in Orlando at RubyConf. I thought my talk went well and the crowd had several interesting questions so I know someone was paying attention. :-) Given that my interests lie in server-side performance and scalability, I saw two linked trends developing: Threads suck (on Ruby?) They work reasonably well in Java but you should avoid t
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Taming Rails memory bloat | Mike Perham
Migrating from redis-namespace | Mike Perham
Public Relations Blast | Mike Perham
http://www.mikeperham.com/memcache-client/classes/MemCache.html