Jacob Santos

You know, whenever someone tells me I can’t do something or that something I think is possible is impossible, it makes me try even harder to prove them wrong or in most cases, prove them right. Either way, both sides comes out great. I say that because it proves nothing to the other side if I prove them wrong, because we both benefited from the experience. I’m not out to make fun or embarrass anyone. If I turn out to be wrong, then I learn a valuable lesson of one that will be hard to forget and they get further evidence to use for the next guy that challenges them.

Win/Win.

I’m going to try even harder now that enough people are saying that I’m not right (which is nicer than saying I’m wrong) on Just-in-Time compilation benefits for PHP. I really do think the extra seconds saved will great impact what PHP can be used for in the future. Judging from a working PHP 4 compiler, it cuts the time in half. Let us say for a moment that you have to process 100 datasets that takes .15 seconds each iteration. That is 15 seconds. If you compile it and it only takes .075 seconds, then well, it would only take 7.5 seconds. It is a poor example, but the point I’m trying to make is if you cut the time, even by a fraction, it can save a lot within a loop.

Yeah, sure it isn’t going to be a huge deal for front end sites because they won’t have anything that within a loop that takes that long. Even if they had a loop, they would use caching so that users wouldn’t notice the speed decrease. If you are doing gaming, math intensive, or heavy processing, it can get ugly very fast and limit you quickly on what you can afford to do time and processing on shared hosts.

The only way to know for sure whether or not JIT will benefit users, is to have a working and optimized solution for which testing can occur. My ultimate goal and I hope by next year I’ll have a working version that can be tested. Along the way, I have other side quests I need to complete before I can get from point ‘A’, which is not having JIT implementation, to point ‘B’, where I have a working implementation.

Not that I care whether or not it speeds PHP up, it would be nice. By this time next year I would know a lot more about Python than I do now and PHP JIT would be less important. My motivation is more compiler theory and always wanting to do something like this. The wealth of knowledge within the Zend and PHP engines is massive and anyone would learn a great deal tweaking and lurking around within them.

So, something next year, I want to either prove I’m right (hopefully that will be the case) or I’ll just prove what everyone else is saying and slowly bow my head momentarily in shame.

Possibly Related Posts:

• Easier APIs for WordPress
• Libraries Should Use Liberal Licenses
• Why Writing Documentation Wasn’t a Waste of Time
• Contradiction of Good Object-Oriented Design
• WTF Are People Still Writing PHP Template Engines

Tags: humor, just-in-time, opcode, PHP

This entry was posted on Monday, April 23rd, 2007 at 8:10 am and is filed under Programming. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.