iBlog - Ilia Alshanetsky - Comments

Emil Vikström: Mail Logging for PHP 5.3+

nospam@example.com (Emil Vikström) — Tue, 09 Mar 2010 12:53:50 -0500

Great work! We have had our own script (in sendmail_path) for a few years now, but this is really the right way to do it!

Another great option would be to provide your own e-mail headers, but I agree that this is enough default values for most cases.

Once again, great work!

tomtom: Reverse MD5 Search Aggregator

nospam@example.com (tomtom) — Sun, 28 Feb 2010 17:47:17 -0500

try: http://md5hashcracker.appspot.com/

David: MD5 Dictionary Attacks

nospam@example.com (David) — Thu, 25 Feb 2010 04:16:32 -0500

Any system should use some salt
It makes your system more secure, for some of you looking for a tool to hash string, I'm using this online md5 converter
David

Alex Kerr: My Thoughts on HipHop

nospam@example.com (Alex Kerr) — Mon, 08 Feb 2010 08:06:58 -0500

> 2. ... This means anytime you need to make even most trivial of changes you will need to go through to convert > compile cycle...

So what about the interpreter FB mentioned in the announcement that gets around precisely this problem as I understand it, and that is currently being used by their engineers? Called something like HPHPi I seem to recall...

Mark Baker: My Thoughts on HipHop

nospam@example.com (Mark Baker) — Thu, 04 Feb 2010 09:32:41 -0500

I believe that HipHop does use its equivalent to zval when variables change their type within their scope, so it may be necessary to refactor code a bit to ensure that variables are effectively strong-typed to take real advantage of this.
That's probably a good thing: weak typing might make PHP easy for new developers to learn because it is forgiving; but enforcing strong-typing is good parctise anyway, and can potentially provide additional benefits with the HipHop optimiser. To take full advantage of that, type hinting should probably be extended to cover basic data types (rather than simply classes) somewhere down the line.

Ilia Alshanetsky: My Thoughts on HipHop

nospam@example.com (Ilia Alshanetsky) — Wed, 03 Feb 2010 19:17:19 -0500

PHP is already thread-safe, what is not thread-safe are some of the libraries various PHP extension may use. Which makes the installs that utilize them not thread-safe, the engine of PHP and "core" extensions are all thread-safe already.

As far as forking goes, on *nix systems it is extremely fast already.

Matt Kukowski: My Thoughts on HipHop

nospam@example.com (Matt Kukowski) — Wed, 03 Feb 2010 18:52:46 -0500

Something that no one seems to mention about HipHop is the fact that they mentioned they made PHP 'thread safe'.

He also mentions that database connections will be sped up as a result because of the use of threads, which can be reused or created much faster than forking a process.

What are your thoughts about the thread safe aspect of HipHop?

Ilia Alshanetsky: My Thoughts on HipHop

nospam@example.com (Ilia Alshanetsky) — Wed, 03 Feb 2010 09:25:05 -0500

HipHop uses a much more optimal memory model then native PHP, since it does not use zval structs to store variables. I would imagine you could easily lower your memory consumption by 30 or more %.

Mark Baker: My Thoughts on HipHop

nospam@example.com (Mark Baker) — Wed, 03 Feb 2010 09:21:49 -0500

Everybody seems to be talking about the speed of hiPHoP, but are there any memory savings?

Servers with insufficient memory can also affect page generation times, if there's insufficient memory for all the Apache threads to avoid swapping.

Torsten: Igbinary, The great serializer

nospam@example.com (Torsten) — Wed, 03 Feb 2010 09:13:34 -0500

Ron, it's a good idea to add something like "asBinary" to the native serialization routines. The compression rate and the increase of speed is such impressive and in most cases I'm able to use binary data instead of clear text.

Torsten: My Thoughts on HipHop

nospam@example.com (Torsten) — Wed, 03 Feb 2010 09:02:04 -0500

For those who run high traffic sites and have done their homework in the optimization of their PHP applications, HipHop would certainly be a interesting PHP implementation. Anyway, I'm excited to see HipHop's influence to the PHP world...

David Caunt: My Thoughts on HipHop

nospam@example.com (David Caunt) — Wed, 03 Feb 2010 08:48:24 -0500

Agreed - this optimisation comes after due diligence, caching and database optimisation

Ilia Alshanetsky: My Thoughts on HipHop

nospam@example.com (Ilia Alshanetsky) — Wed, 03 Feb 2010 08:41:48 -0500

You'd be able to get a speed boost only if PHP is your primary bottleneck, I'd wager that for majority of people that is not the case.

If you page takes 200ms to deliver and 160ms of it is DB interaction, the 20ms speed-up won't make any visible difference.

David Caunt: My Thoughts on HipHop

nospam@example.com (David Caunt) — Wed, 03 Feb 2010 08:37:24 -0500

Nice analysis of HipHop.

In response to comment #5, if I can half the time my users spend waiting for a HTML document, and I can automate the deployment process sufficiently, I think it's a worthwhile performance improvement.

The divergence issues are the greatest for me. If my application runs differently in development (PHP) than it does in production (HipHop), that's not much good. Increased testing, QA and development cycles will never be more expensive than the performance loss.

Rahim: My Thoughts on HipHop

nospam@example.com (Rahim) — Wed, 03 Feb 2010 08:12:58 -0500

Most of the sites do not need HipHop. In most cases bad sql query and too many tcp connection are the bottleneck. Only huge sites like facebook need HipHp and they have also the capacity to convert the php extensions to HipHop.