810 karma · joined July 29, 2010
http://morganpyne.com
A master of all trades, the father of a beautiful flame, a player of gypsy jazz, an aspiring luthier, an explorer on and below the ocean.
More info on hiera-gpg here: http://www.craigdunn.org/2011/10/secret-variables-in-puppet-...
http://www.percona.com/doc/percona-toolkit/2.1/pt-online-sch...
I wonder would they do it again with the benefit of hindsight, or did it serve their purpose?
http://www.bbc.co.uk/news/uk-politics-17576745
I think you are deluding yourself though if you believe that most major govts are not doing wholesale digital trawling to the best of their (advanced) abilitites already, regardless of whatever legislation is currently in place.
This feature caught my eye: - Combines multiple CSS or JavasScript requests into one request to reduce the downloading time
I wonder how they achieve this at the webserver level? Normally something like this is done as part of the deployment/compile process. Anybody familiar with Tengine care to comment?
Running migrations on live databases with lots of data in them is hard. There are many strategies to work around this problem, but generally running an 'alter table' on your primary db server on a huge table while it is in use should be your very last option.
The Percona pt-online-schema-change tool goes to great lengths to avoid this kind of problem.
A conservative estimate of 20MB per PHP process would already put the requirements for 220 of them at over 4GB (twice what you have) and that's not allowing anything for the OS and anything else running on the machine. Its not an exact science figuring out the appropriate MaxClients, but you should find out how much the rest of the machine needs, look up the average Apache process size (ps), divide the available memory by that and then reduce it a little. Use this as you starting point for figuring out the MaxClients. Keep an eye on the available free memory for a while (vmstat) and gradually up that limit until you reach a comfortable working level for the setting.
Unlike the one above, it doesn't require any code changes (it's a C-based PECL extension), and can easily be set up to be triggered via a parameter on the URL or to profile every nth page load (via a simple auto-prepend) for usage in production environments. It produces a full callgraph (using graphviz), you can drill down into the profile interactively, and you can record and compare profiles over time of the same page. It's also really quick and easy to setup and use.
There are of course other extensions that can do some profiling such as APD and XDebug, but xhprof is my personal favourite. I'm not sure I would ever be keen on confining my profiling to a PHP profiler written in PHP, although you do get some similar functionality from some frameworks such as debug mode in the Symfony framework.
Although apparently the sentiment even predates his usage of it by about 60 years.