Search results matching tags 'PHP' and 'Garrett Serack'

Crafting a Better PHP Build Process on Windows – Part IV

Anonymous — Wed, 24 Jun 2009 00:12:00 GMT

In the previous post, I discussed what it took to use PGO on the Windows PHP build. That led to me building automated build scripts...

Automation as the root of all evil

"Anything that can be done for you, automatically, can be done to you, automatically." - David C. Wyland

First, I had to get the entire dependency stack into the mix. While some of the dependent libraries had VCProject files, some didn't. Worse, even if they had them, you couldn't tell with a degree of certainty that they were compiled with the same settings which would enable them to take advantage of PGO optimization.

I began taking each project, updating (or creating, using the Trace and mkProject tools) the Visual C++ project files that would use the same settings as the rest, and eventually came up with a solution file that had 74 projects in it - some of the projects generated more than one binary.

Next, I had to actually automate the process of creating the vcproject files. Once you've got the right dependencies, the PHP build process cranks out over 30 binaries when you include the PHP extensions that get built as part of the core.

After what seemed like a million compile-verify-tweak iterations, I had the tools that could generate VCProject files for the core PHP and all the extensions, provided it was all in the right place.

Next I wrote a .cmd batch script that went step-by-step, checking out the source, compiling the dependent libraries, building the PHP makefile, compiling PHP like the community did - and logging what it was doing, then switching to instrumentation, rebuilding the dependencies again, building the stack, PGO training it with test data and some applications (Wordpress, MediaWiki and phpBB) and then relinking it with optimization.

I got the .cmd script almost working, but it was fairly fragile. At that point I decided to switch batch scripting strategies and, in about a week, rewrote the batch script in JScript, which was far more flexible, and a lot more reliable.

What's next...

"The future always arrives too fast... and in the wrong order." - Alvin Toffler

During this process, I tweaked the build process that is generated quite a bit, adding in a few more applications to the PGO training, which cranks the performance up more and more.

Now, I can add in more scripts to assist with the training pretty trivially, but it still takes some effort to package up an entire application like MediaWiki or Wordpress and include it into the build process.

Even once I've added in an application, I end up doing a whole slew of comparative testing to see what impact it has on the final executables.

As time goes by, I'm sure there will be more tweaking to be done but, in all likelihood, any significant performance gains are going to be the result some modification of the PHP codebase itself.

Crafting a better PHP build process on Windows – Part 1

Anonymous — Tue, 09 Jun 2009 18:22:00 GMT

The last several months, I've been working very deeply with PHP - specifically, compiling the PHP core itself, and looking for avenues for optimization. This is the first of four posts about the journey I've been on with PHP.

I get started building PHP

"It is a bad plan that admits of no modification" - Publilius Syrus

I started working with building PHP itself about a year ago. Initially, I was trying to put together an environment to compile up the PHP stack so that I could do some debugging, and track down a few faults that we were encountering in some of the PHP applications that we were trying to modify to use the SQL Server PHP driver that the SQL Server team here at Microsoft was creating.

Once I began to work with the source code, I found out very quickly that on top of having a hard time recreating the exact same binaries that the community build process generated, there were a large number of dependent libraries that were available in binary-only form and which were kept in a zip file that was passed around from developer to developer. That seemed a little odd for an open-source project, but I can certainly understand that over time, unless someone is working hard to keep it all together, these things happen.

Around the same time, the community had started to invest time and effort to 'clean up' the dependencies for building PHP on Windows, and move towards supporting VC9 (Visual Studio 2008) as an officially supported compiler.

In order to help in this process, I built out some testing environments in our Lab, which would let me compile up PHP on Windows and Linux, in order to get decent and reliable test results which we could use to identify any shortcomings that we could then address. This includes benchmarking not just the core PHP executable, but replicable and comparable testing of PHP applications such as Wordpress, MediaWiki, Gallery and phpBB.

PHP 5.3 on Windows: Not your father's PHP

"I'm looking for a lot of men who have an infinite capacity to not know what can't be done." - Henry Ford

For PHP 5.3, Pierre (and others) had gone out and found up-to-date versions of all the dependencies, brought them together, and managed to get them compiling with VC6 and VC9. They had posted these in binary and source form to the PHP Windows Internals site, which allows anyone to rebuild the PHP stack on Windows and, theoretically, get the same results as the 'official' build.

Jumping in at that point was much easier than it had been, as all you had to do was download the binaries of the libraries, check out the source code, run a few commands at the command line and, presto, you had your PHP executables.

At this point Pierre and I played around with the build flags on VC9 and found some settings that gave some pretty significant improvements to the speed of PHP vs. the speed of the VC6 version -and a lot of speed improvements vs. the old 5.2x line of PHP.

In Part II, I'll talk about going one step further with optimization.

Crafting a Better PHP Build Process on Windows – Part I

Anonymous — Tue, 09 Jun 2009 18:22:00 GMT

I get started building PHP

"It is a bad plan that admits of no modification" - Publilius Syrus

PHP 5.3 on Windows: Not your father's PHP

"I'm looking for a lot of men who have an infinite capacity to not know what can't be done." - Henry Ford

In Part II, I'll talk about going one step further with optimization.

PHP 5.3 RC2 Highly Optimized for Windows

Anonymous — Mon, 11 May 2009 16:52:00 GMT

Howdy,

I've been working for many months with Pierre Joye - well, really many people in the PHP community - on getting PHP to run faster on Windows.

Pierre has been working rapidly on upgrading libraries (Pierre pioneered the work to get PHP and its hoard of dependent libraries updated and properly compiling on Windows), replacing old POSIX-emulation code with native calls, patching bugs, and about a million other things, all of which had a huge impact on performance and stability of PHP on Windows.

For my part, I've been spending my time behind the scenes by feeding information to Pierre that he needs, testing, analyzing, and finally by constructing a new build process that enables us to take advantage of some pretty sweet optimization technology in Visual Studio.

Starting today, you can find snapshot builds of PHP 5.3 that are built using my optimized build process on the windows.php.net site.

A few notes:

Over the course of the next couple of weeks, I'll be explaining how this build process works, and making available the tools that make it all possible.

Only the non-thread-safe version is available, so you need to use FastCGI with IIS in order to use it.

Since this is a radically different build than the ones that had been traditionally used to create the Windows PHP binaries, you should download the binaries and test with them, but you probably should avoid using them in production just yet.

If you have any feedback about the builds, leave me a comment, or email me.

How a cowboy spends two days in Boston: Drupalcon 2008

Anonymous — Mon, 24 Mar 2008 21:45:00 GMT

Howdy ya'll,

I was recently in Boston, and managed to spend a couple of days at Drupalcon, where Port25 was a silver level sponsor for the event. The herd was over 800 attendees--all focused on Drupal. Needless to say, I was duly impressed.

What's Drupal?

Drupal, written in PHP, is an open source content management platform. It's equipped with a powerful blend of features, and supports a variety of websites ranging from personal weblogs to large community-driven portals. Drupal has been rapidly displacing a large number of other PHP based content management systems, and has an active community along with broad vendor support.

Over the last year or so, Microsoft has been working hard to improve PHP's support on Windows. With the hard work from the SQL Server team, who recently published a new CTP of the native SQL Server PHP driver, the FastCGI work that the IIS team has done, and of course Zend, who we've been coordinating with--PHP is rapidly getting the support and attention it deserves.

So... Drupalcon?

Ah Yes. From the humble beginnings in 2004, where 10 people attended the first Drupalcon, it's grown into a massive bi-annual event (one in North America, and one in Europe) with over 800 attendees, plus sponsors. I was truly stunned at the sheer size of the event--I would have assumed a much larger affair.

Kieran Lal hosted a session early on Monday morning, in which he told how to get the most out of Drupalcon--and really, it was applicable to any conference, and I really enjoyed it. Between that session and the first keynote, I hung out, and got to know a bunch of folks.

Who are the people in your neighborhood?

Drupalcon was really quite special--of all the conferences I've been to, Drupalcon was home to the most friendly folk I've ever seen. Everybody was really fun to talk to, and they all were excited to hear about Microsoft's effort in making PHP run great on Windows.

I spent about 45 minutes talking to Larry Garfield about expanding support for databases in Drupal. Larry has done a tremendous amount of work for Drupal 7 on database abstraction--it's going to be pretty cool, trust me.

I managed a few minutes of Kieran Lal's time, which was quite amazing, as he seemed to be doing a million things at once during the conference, and barely had a spare moment to catch his breath. We talked about the future of Drupal, and how Microsoft could get involved, and I think we're both pretty excited about the future.

Dries Buytaert gave his traditional "State of Drupal" presentation (video can be found here), which contained a couple real eye openers:

- Drupal 6 had over 100,000 downloads in the first month of release, that's 2x over Drupal 5. Wow. That's
pretty amazing.
- Drupal 7 (and beyond) appears to have one of the most well thought out plans in place--I can't recall another open source project that has such a detailed road map.

Then, I came home...

Aside from the jet-lag and the shortness of the trip, I enjoyed the conference immensely. We've been playing with Drupal in our lab over the last several months, and it's clear that the time has been well spent--Drupal is not only an emerging phenomenon, but the future looks even brighter. I reckon you'll be seeing many more posts from me in the future about it.