Comments for Oleksiy Kovyrin

Comment on New Chapter: Swiftype by Andrew B.

Andrew B. — Wed, 22 May 2013 20:20:00 +0000

Good luck on your new gig!

Comment on New Chapter: Swiftype by fxposter

fxposter — Wed, 22 May 2013 08:45:00 +0000

Congrats!

Comment on New Chapter: Swiftype by Looking for a New Gig « Oleksiy Kovyrin

Looking for a New Gig « Oleksiy Kovyrin — Wed, 22 May 2013 01:52:00 +0000

[...] Ok, I’ve found a new job – I work for Swiftype now! window.fbAsyncInit = function() { FB.init({appId: [...]

Comment on Looking for a New Gig by New Chapter: Swiftype « Oleksiy Kovyrin

New Chapter: Swiftype « Oleksiy Kovyrin — Wed, 22 May 2013 01:49:00 +0000

[...] after a few weeks of looking for a new job I’m really excited to start my journey in a young, but very ambitious startup called Swiftype [...]

Comment on Momentum MTA Performance Tuning Tips by Chris Nagele

Chris Nagele — Wed, 22 May 2013 17:27:00 +0000

Yeah, that makes sense. We wanted to test Message Systems but had the same feeling. I was just curious if you did any benchmarks. The fact that these mail servers are so configurable locks you in a lot. We’ve been really happy with PMTA though.

Comment on Momentum MTA Performance Tuning Tips by Oleksiy Kovyrin

Oleksiy Kovyrin — Wed, 22 May 2013 17:23:00 +0000

The thing is, we’ve already invested too much into momentum + there is not much reason to look for other solutions when our current solution works pretty well.

Comment on Momentum MTA Performance Tuning Tips by Chris Nagele

Chris Nagele — Wed, 22 May 2013 16:26:00 +0000

Have you tested PowerMTA from Port25 at all? We use it for Postmark, and most large ESPs like Mailchimp and Campaign Monitor use it these days.

Chris

Comment on Momentum MTA Performance Tuning Tips by Daniel Sydnes

Daniel Sydnes — Wed, 22 May 2013 01:01:00 +0000

“When Momentum receives a message, it stores it to the disk (as required by SMTP standard) and then tries to deliver the copy it has in memory, if delivery succeeds, on-disk copy is unliked.”

I don’t like it much either, but it is a well established standard.

Perhaps you meant “unlinked”?

Comment on Momentum MTA Performance Tuning Tips by Tom Mairs

Tom Mairs — Wed, 22 May 2013 04:12:00 +0000

Great blog – you are dead on with your recommendations. As an SE for Message Systems I recommend EXT2 for the message spool whenever possible (sometimes it is not an option). Another key to improving performance is keeping OS, Logs, and Spool on separate arrays if at all possible. RAID10 provides the best performance for the spool array, whereas RAID1 works best for OS and Logs. Thanks for sharing!
Tom Mairs, SE Manager at Message Systems

Comment on Quick (and dirty) Patch for Ruby Enterprise Edition 2011.03 to Prevent Hash Collision Attacks by Arthur

Arthur — Wed, 22 May 2013 10:19:00 +0000

Applied it with RVM, installation works fine and seems to produce a working, patched, ree version.
This should do it on any RVM enabled system:
# Update RVM, just to be sure.
rvm get latest
rvm reload
# Get and install the patch
wget https://raw.github.com/gist/1535569/b59b5e3e753288fa7a2f23d640a285775ab0879b/ruby-1.8.7-hash-randomize.patch
rvm install ree –patch ./ruby-1.8.7-hash-randomize.patch