I’ve been busy


Yeah, I know, I still haven't closed my Celery replacement issue. Our Celery farm has been quiet lately, and we've had a lot of other irons in the fire. A demo of our product running in a new context with a new UX, a cool new disambiguation feature, and some other goodies. I'll return to … Continue reading I’ve been busy →

Gotta get going on my Celery experiments


I've wanted to try some Celery alternatives but I've been super busy! We've been trying to roll out a new release of our product, and maybe this week we'll finally get 'er done. Then I can spend a few days experimenting with other packages and thinking about code migration.

I switched from Cacti to Munin


This week, I switched our systems-level monitoring from Cacti to Munin. I was dissatisfied with Cacti's interactive-only configuration and limited OOTB charts, and its reluctance to correctly display the processor %U of my multicore servers. I tried the oft-cited suggestion of cloning the existing %U graph into a new template and bumping the maximum to … Continue reading I switched from Cacti to Munin →

Alternatives to using Celery


I've found some candidates for replacing Celery in my company's product. (My reasons for replacing it are elucidated here, here, and here.) I got these from web trawling, blog comments, and some e-mail. At first blush, none of the candidates have any disqualifying attributes, except for lacking subtasks. Celery is the only Python-friendly asynchronous task … Continue reading Alternatives to using Celery →

Nook networking blues


My wife owns a NOOK Simple Touch with GlowLight. Our home router in an Apple Airport Extreme, the latest model. The NOOK worked flawlessly when she first got it. But starting three weeks ago, it forgets our home network credentials about once a week. Nothing's changed in our network configuration. The Airport's location hasn't changed. … Continue reading Nook networking blues →

My requirements for replacing Celery


I'm ready to start looking at candidates to replace Celery in my company's product. (The reasons are elucidated here, here, and here.) Our SaaS product provides data mining and visualization for intellectual property. A 10-second elevator pitch is, it's as though we attached Microsoft Excel's chart wizard to US and international patent offices. ("As though" … Continue reading My requirements for replacing Celery →

Breakage when upgrading from Celery 2.5.3 -> 3.0.4


Commenting on my update to my Celery rant, @asksol asked me to post the Pylint results that made me question the claim of backwards compatibility. ("@Asksol asked" — See what I did there? That's alliteration. It's a sign of a quality blog post. Ask for it by name.) Again for the record, @asksol is a … Continue reading Breakage when upgrading from Celery 2.5.3 -> 3.0.4 →

An update to my Celery rant


An update to my rant on Celery's frequently-changing API: I've decided to stay with Django-celery 2.5.5 and Celery 2.5.3. When I tried using Celery 3.0.4 with my existing code, Pylint threw about 60 warnings, many of which look real and all of which weren't there when I used Celery 2.5.3. "Backwards-compatible" my ass! I shouldn't … Continue reading An update to my Celery rant →

Celery API changes drive me nuts


This is a rant. My company's code base is over 65K lines of Python and JavaScript code. We use Celery, Django-Celery, and RabbitMQ for our background asynchronous tasks. Ten different tasks.py files contain 30 task classes, split roughly 50-50 between periodic and on-demand. We use subtasks. Today, I dug into updating from Celery 2.5.3 to … Continue reading Celery API changes drive me nuts →