This link has been bookmarked by 129 people . It was first bookmarked on 09 Jul 2006, by craig hancock.
-
26 Aug 11
-
15 Oct 09
-
29 Aug 09
-
05 Aug 09
-
02 Jul 09
-
15 Apr 09
-
16 Feb 09
-
23 Nov 08
-
10 Jul 08
-
07 Apr 08
-
06 Apr 08
-
26 Mar 08
-
20 Mar 08
-
25 Feb 08
-
17 Feb 08
-
This article addresses the all-to-common false assumptions about the cost of scalability and performance in PHP applications.
-
Performance is measured by the output behavior of the application. In other words, performance is whether or not the app is fast.
-
Scalability is the ability of the application to maintain good performance under heavy load with the addition of resources.
-
200 million page views per month, and they’re able to handle it with only 3 web servers and 8 small database servers
-
MySQL has had a reputation for being slow in the past, but most of that seems to have come from sub-optimal configuration and the overuse of MyISAM tables. Owen confirmed that the use of InnoDB for tables for read/write data makes a massive performance difference.
-
one being the need for large amounts of slave databases.
-
he responded by saying, “none of the scaling challenges we faced had anything to do with PHP,” and that “the biggest issues faced were database related.” He even added, “in fact, we found that the lightweight nature of PHP allowed us to easily move processing tasks from the database to PHP in order to deal with that problem.”
-
After doing some research, I found that by using a combination of Apache 2’s worker threads, FastCGI, and a PHP accelerator, this was no longer a problem.
-
Digg is in the process of preparing to scale to 10 times current load. I asked Owen Byrne if that meant an increase in headcount and he said that wasn’t necessary. The only real change they identified was a switch to a different database platform. There doesn’t seem to be any additional manpower cost to PHP scalability either.
-
I suggests the common MySQL MyISAM good / InnoDB bad misconception I often see these days. MySQL is somewhat unusual in that it offers multiple storage engines.
-
apache benchmark
-
PECL extension to have PHP call the Java code
-
changing their architecture to use memcachd and "shards"
-
If I were writing a web application serving data in multiple presentation formats (for example HTML, WML) would PHP still be a suitable platform? Are there any other businesses using PHP in a similar situation.
-
how to optimise PHP in order to 'compile' only once
-
-
17 Jan 08
-
20 Nov 07
-
25 Oct 07
-
16 Oct 07
-
10 Oct 07
-
03 Jun 07
-
08 May 07
-
05 May 07
-
30 Apr 07
-
25 Mar 07
-
24 Mar 07
-
14 Mar 07
-
09 Mar 07
-
23 Jan 07
-
12 Dec 06
-
27 Nov 06
-
23 Nov 06
-
12 Nov 06
-
26 Oct 06
-
24 Oct 06
-
22 Oct 06
-
16 Oct 06
-
28 Sep 06
-
25 Sep 06
-
31 Aug 06
-
29 Aug 06
-
21 Aug 06
-
10 Aug 06
andreyevSeveral weeks ago there was a notable bit of controversy over some comments made by James Gosling, father of the Java programming language. He has since addressed the flame war that erupted, but the whole ordeal got me thinking seriously about PHP and its
php programming performance work for:gnustavo for:danielfl for:lmaxcar
-
04 Aug 06
-
03 Aug 06
-
02 Aug 06
-
28 Jul 06
-
27 Jul 06
-
09 Jul 06
-
07 Jun 06
-
20 Apr 06
-
18 Apr 06
-
17 Apr 06
-
14 Apr 06
-
13 Apr 06
-
-
12 Apr 06
-
Digg PHP's Scalability and Performance - O'Reilly ONLamp Blog
php server tuning setup scalability performance programming digg
-
11 Apr 06
gallox smithThis article addresses the all-to-common false assumptions about the cost of scalability and performance in PHP applications.
-
beattakeshi"This article addresses the all-to-common false assumptions about the cost of scalability and performance in PHP applications."
-
10 Apr 06
-
KurtIt turns out that it really is fast and cheap to develop applications in PHP. Even as a self-proclaimed PHP evangelist, I was very startled to find out that all of the theories I was subscribing to were true.
Page Comments
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.