Port 25: The Open Source Community at Microsoft : Garrett Serack

Crafting a Better PHP Build Process on Windows – Part IV

Garrett Serack — 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 II

Garrett Serack — Thu, 11 Jun 2009 20:10:00 GMT

I talked about getting started in building the PHP stack in my last post, now I'm taking it...

One step further

"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." - Donald Knuth

A chance conversation I had last summer at OSCON with Trent Nelson - who was building Python on Windows - planted the seeds of how to get PHP on Windows optimized further. Trent was using the PGO features of Visual Studio to generate Python binaries that run faster.

Rather than spend a lot of time optimizing all the little bits of PHP itself, I thought that this would be an ideal way to improve the overall speed of PHP, provided I could find the right scenarios to train PHP with. Little did I know that finding the right scenarios wasn't the hardest part.

What is PGO? (from Wikipedia)
Profile-guided optimization (PGO) is a compiler optimization technique in computer programming to improve program runtime performance. In contrast to traditional optimization techniques that solely use the source code, PGO uses the results of test runs of the instrumented program to optimize the final generated code. The compiler is used to access data from a sample run of the program across a representative input set. The data indicates which areas of the program are executed more frequently, and which areas are executed less frequently. All optimizations benefit from profile-guided feedback because they are less reliant on heuristics when making compilation decisions.

Adding PGO to the existing build process

"I have not failed, I've just found 10,000 ways that won't work." - Thomas Edison

I had downloaded the source to the dependent libraries off the PHP wiki, checked out the PHP source code, and begun the process of adding in PGO support to the existing build process. This proved to be extremely difficult.

Even limiting the scope to just the core of PHP itself - without the dependent libraries - I ran into trouble trying to compile using PGO instrumentation and then re-linking after running some tests. The make file that gets generated by the configure.js script (a JScript version of the automake configure script for the Windows platform) was just not built with what I had in mind.

I spent the better part of two weeks trying different approaches to tweaking the makefile so that I could use PGO to improve the PHP executable, but I kept running into roadblocks. Worse, the closer I got to a makefile that did what I wanted, the farther away from the current build process I was getting, and I wasn't sure that what I would end up with would even be close to what was being built today.

The long dark winter road

"Only the meek get pinched. The bold survive." - Ferris Bueller

I came to the conclusion that I'd have to build new Visual Studio project files from scratch. What worried me was that this would end up to be a completely different build process, and I'd never get the community to abandon what was already working, so I'd better be able to rebuild these new project files easily.

I started looking (inside Microsoft and out) for any tools which generated Visual C++ project files. I found someone internally who had used some JScript to create project files from text files, but after some experimentation, I found this was nowhere near what I needed. What I really needed was a way to convert the generated Makefile into a .vcproj file-and not just 'wrap' it.

Once I found there was no such tool* , I began trying to figure out how to create one. I had this idea a few times in the last decade or so: watch how a program is compiled, and create a project file that does the same thing. Having tossed around the idea in my head before, I knew it wasn't going to be trivial but, without it, I couldn't do what needed to be done.

* Let me tell you: you never want to think about writing a tool to parse out what a makefile does. It's rather like making a tool that tells you how sausage is made, in excruciating detail. Ugh.

In Part III, I'll talk about the trouble with observing the build process.

Crafting a Better PHP Build Process on Windows – Part I

Garrett Serack — 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.

PHP 5.3 RC2 Highly Optimized for Windows

Garrett Serack — 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.

A funny thing happened on the way to ApacheCon

Garrett Serack — Thu, 10 Apr 2008 18:20:00 GMT

Back in January, I invited the Apache Software Foundation to attend the Windows Server 2008 Application Compatibility Labs, here on our campus in Redmond.

The week that Apache was here, was so valuable for both groups--the product groups got to see and understand what some of the issues were that some of the Apache projects have run into, and the Apache folks were able to get their hands on the developers who built the system.

Myself and Bill Rowe had hammered out some details before I actually sent the invitation out. Along with posting it on some of the Apache Mailing Lists, I also posted the invitation on my own blog so that others could see what we're up to. And, as to be expected, there was a wide variety of comments posted--both positive, and ... less positive.

My favorite though, was: "Microsoft should go to Apache developers and see if Windows Server 2008 works correctly with Apache, not the other way around."

In some ways, that would have been somewhat impractical--when the Apache folks visited us, they had the opportunity to meet with engineers and program managers from many different groups, in addition to getting access to the hardware in the lab and the expertise of the folks who run that. For us to pick up the 20 or so people from the product groups that they actually met with, and drag them all out to all the locations where Apache developers are--which is pretty much everywhere--would not have been possible

Still, I felt it would be more than valuable for me to go ApacheCon, so that I had the opportunity to meet with Apache developers where they roam. When Bill was in Redmond, he invited me to the Apache Hackathon--the couple of days at the beginning of the conference that developers could hang out and code. So, a snappy 10hr flight later, here I am at ApacheCon in Amsterdam.

The Apache Foundation is an interesting community--or rather community of communities. It's not just one project (the http server is what most people think when they hear Apache), but literally dozens of top level projects, and a whole bunch more in the 'incubator' (where baby projects are cultivated until it is clear that it will have ongoing support and development). The hackathon is just a large room with tables where folks can come in, sit down open their laptops and start coding. It's actually a lot quieter than I imagined it would be. Naturally, the folks in communities tend to gravitate together and discuss their projects.

As I'm not really on any project, I've been bouncing around chatting up different groups, getting their perspective of their own little chunk of Apache. Most of the people I've talked to aren't surprised at all that I'm here--which is definitely a change from conferences a year ago--and are excited to hear about our efforts.

Now, for the funny thing. I booked my hotel a few weeks back, using the internal travel system here at Microsoft. The hotel that the conference is at was booked, so I looked for one nearby. Unfortunately, the tool doesn't let me search for hotels near another hotel, and I didn't know what else was close that I could search near (and my inability to read Dutch didn't help), so I used the tool to show me where the hotels were, I'd switch to http://local.live.com and see how close it was, and if it was close, I'd switch to the other tool to check out the availability, and there was not much available. ... I guess I was distracted while I was doing it, and I ended up booking a hotel right next to the airport, which is in no way close to the conference, and so I spent the night in that hotel--and called the wonderful travel support folks who found me a hotel where I needed to be, and I moved there the next morning. Lesson learned: next time I travel to the Netherlands, I'm asking Hank to find me a hotel.

How a cowboy spends two days in Boston: Drupalcon 2008

Garrett Serack — 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.

The Apache Visit to the Microsoft Campus: Day Three

Garrett Serack — Mon, 03 Mar 2008 20:00:00 GMT

Day two moseyed late into the night...well for me anyway--cowboys wake with the sun.

Day three turned out to be a day full of surprises for me--most of the sessions were significantly more interesting than I would have guessed.

We started the day with a presentation by Bill McKinley on Windows Logo Certification (for which there is a great little quickie primer here). I highly recommend checking this out--the logo certification program provides some tools to assist with certification validation, and even if you have no interest in certification, running the tool will give you a rundown of potential issues that your customers will face.

After a break for more testing, Rob Mensching and Peter Marcu dropped by to give the team a thorough examination of WiX (the open source Windows Installer XML toolset). Again, very cool stuff. Admittedly, there seems to be a somewhat steep learning curve, but it integrates nicely into build scripts, and has all the flexibility you'd ever need.

After lunch, we did some testing, with a quick little jaunt to the Microsoft Company Store, where the attendees took advantage of Microsoft Employee pricing on some software and hardware.

We rounded out the day with a session on Windows Error Reporting -- you know when an app crashes, and you can send anonymous debug info to Microsoft? The information ends up in the WER system, where developers can register to get crash and hang information for their software and drivers. I knew that the information was collected, but previously, I had no idea how easy it is for app developers to get their hands on the data. I strongly recommend that you check it out.

While Wednesday was the last day for most of the attendees, a few stayed through Thursday, and I'll post a wrap-up on that tomorrow.

The Apache Visit to Microsoft Campus: Day Two

Garrett Serack — Thu, 28 Feb 2008 22:59:00 GMT

The Apache Visit to Microsoft Campus: Day Two

Day two turned out to be quite a busy day!

First thing in the morning, we started off testing some Apache applications on Windows Server 2008, both the 64 and 32 bit versions. Right away, a few things were uncovered, primarily around UAC, data redirection (where Windows redirects writes to the file system and registry to safe locations for low-rights processes) and an odd issue with an event mutex that we're tracking down.

After getting a little testing done, we had a great in-depth presentation of IIS by Senior Program Manager Thomas Deml. Like the Core Networking presentation the day before, it was really informative, and the Apache folks took the opportunity to really drill down into the architecture of IIS. Why would they? Like I mentioned before, a number of Apache Projects (like Tomcat) support IIS in one way or another, and could benefit from tighter integration with IIS.

After lunch, Peter-Michael Osera and Li Shao spent a couple of hours addressing some of the C++ and toolset questions the Apache team brought. They really did an admirable job answering the questions that they could, and the ones that they didn't have answers to, they are following up via email over the next couple of days.

After that, some more time for testing rounded out the rest of the day.

For supper, Sam Ramji, took the team out to Ruths' Chris Steakhouse for a fantastic meal, and we had a great evening talking about nearly everything under the sun.

The Apache Visit to Microsoft Campus: Day One

Garrett Serack — Tue, 26 Feb 2008 20:34:00 GMT

This morning, we've had the honor of hosting the Apache Software Foundation in the Windows Server 2008 Application Labs. They are here this week in order to get some deep knowledge about Windows Server 2008, and access to the folks from product groups who can help them make their apps work better under Windows Server.

We asked them out to campus because we are extremely interested in having the Apache web server (well, all the Apache projects) run great on Windows Server 2008. Now, every time I say that, some folks always want to know "Why would you want that?" or "What do the IIS folks think about that?"

Well, it turns out that some folks have apps that run on Apache. Yes, even on Windows. Sometimes, it's a matter of investment in a particular solution where their app uses Apache. It could even be that they just simply prefer the model that Apache provides. Regardless, it's important to us that those applications run as good as they possibly can on the Windows platform.

As to the question about IIS, there are several Apache projects like Tomcat that currently support IIS, and hey, we'd like to have even better support. To make that happen, we've asked some folks from the IIS team to join us in the labs, where they can open up and give the assistance that is needed.

By midday, two fine gentlemen from the Compatibility Lab (Pat Altimore and Maarten Van De Bospoort) presented a great session about general compatibility issues with Windows Server 2008.

In the afternoon, we had Ari Pernick (along with a posse of extremely knowledgeable folks, whose names I did not get... but I will) come out from the Core Networking group. They spent about two and a half hours going through details in the Windows Server 2008 networking stack, as well as a deep investigation of the HTTP.SYS technology. Now, I’m no slouch when it comes to this stuff, but I tell ya, I learned a lot yesterday just sitting in on that. From the water-cooler conversations that we had later in afternoon, I would expect that we’re going to see some interesting changes in Apache httpd, and Tomcat in the future.

After that, we took an hour and came up with a list of other issues and questions that the Apache folks had, so we can drag in some more product groups on Tuesday and Wednesday.

As for the evening, we all went out to the Rock Bottom Brewery for some food and drinks and some socialization—I took a few pictures, and I’ll get them up as soon as I can.

Garrett Serack: Open Source Software Community Lead

Garrett Serack — Thu, 21 Jun 2007 20:50:00 GMT

I'm pleased to announce ... er, myself, as the Open Source Community Lead here at Microsoft.

I'd have left this to Sam, but hey--why should he get all the fun.

I'm responsible for building communities of Open Source developers around Microsoft's platforms, both externally, and internally--yes, this means the product groups. I'm really interested in what kinds of things we can start building as Open Source software, and illuminating what we've already done.

I said a few things the other day on My blog that I think I bears repeating:

This is a pretty wide reaching role, meaning that I touch a lot of ground. Some of the highlights:

Seeking out Open Source projects we can assist (either by contributing code, MSDN licenses or whatever :D )

Speaking/Presenting with companies, conferences, groups and people

Building an Open Source MVP Program

Enlightening Microsoft Product Groups about Open Source, and finding opportunities for them

Facilitating communication between open source developers and Product Groups

Building transparency into Microsoft and Open Source (believe it or not!)

There have been a lot of changes in Microsoft in the last few years, that folks can't yet see, and I'm hoping to expose that type of thing to the world, and bring the world of Open Source to Microsoft.

I'm not going to espouse the great plans I have in too much detail... I've found that actions speak louder than words, and have far more lasting impact than the words do. I'm focusing on what Microsoft is doing, and less on what has been said. I mentioned that too in my blog:

I don't get it... Microsoft and Open Source? Are you sure?

I know... I know. Y'all got some reservations about Microsoft with regards to open source. Well, I'm not going to try convince you of anything. What I am going to do is to shine the light on the things Microsoft is doing to create communities in the Open Source world.

Add to that, I'm doin' some rustlin' inside of the company itself--as expected, there are a few tenderfoots 'round here who would just soon reckon' we didn't bother. Well, I got a cattle brand heatin' up just for the conversation.... We'll just see about that.

Somethin' about me:

I joined Microsoft in the fall of 2005 as the Community Program Manager of the CardSpace team, and I've been working with companies and the open source community to build digital identity frameworks, tools and standards to shape the future of internet commerce and. I'm also co-writing a book titled Understanding CardSpace, which should be available in the fall of 2007. Prior to moving to the Puget Sound area, I've had a lengthy career as a Software Development Consultant, moving from Developer, to Architect, to Mentor over the course of the last 16 years. As life-long code-monkey, I've pounded out code on more than 20 platforms and 35 different languages, and I see no reason to stop there. I've put code into many open source projects, and I'd like to think that I share a very strong part of the Open Source vision that permeates information technology everywhere. You can catch all my posts on my blog at http://fearthecowboy.com .

What's Next:

In my next blog post I'll detail the promise--that is my commitment to the community. I think it's important to know what you can expect, as well as my boundaries. I'll also have communication channels setup so that you can talk to me; either publicly, or via confidential email.

Garrett Serack

[PostIcon:4108]