News for hackers. Stuff that matters.
Re:The Meteoric Rise of DigitalOcean by jacques_chester on Thursday June 13, 2013 @11:02PM (#5878043)
To add a little bit of anecdata, I recently move from Linode to DigitalOcean.

On Linode I was getting jammed on I/O; on DigitalOcean I am jammed on CPU.

I'd be happy to give up half my RAM to get twice the cores, actually. I run a modest Wordpress network (http://ozblogistan.com.au). Once MySQL is humming, most of the CPU time is spent on various copies of PHP running the increasingly bloated Wordpress codebase.

(Yes, I've used opcode caching. I've never had good experiences with any of the major ones).

Re:The Meteoric Rise of DigitalOcean by pfg on Friday June 14, 2013 @09:15AM (#5879689)
>(Yes, I've used opcode caching. I've never had good experiences with any of the major ones).

Just wondering, what were your experiences? Installing apc is basically apt-get install php-apc (if you're on Debian/Ubuntu), and that's about it unless you want to increase the memory limit. This will greatly reduce CPU usage.

Re:The Meteoric Rise of DigitalOcean by jacques_chester on Friday June 14, 2013 @09:44AM (#5879840)
My experience is that all the ones I've tried freeze up (is eAccelerator even around any more?).

I periodically try again.

Re:The Meteoric Rise of DigitalOcean by pfg on Friday June 14, 2013 @09:55AM (#5879903)
Ah, yes, eAccelerator, I remember that one. Most people are probably using apc nowadays, and I haven't had any problems with it.

By the way: Starting with PHP 5.5, Zend's own opcode cache will be included by default.