[drupal-devel] Drupal.org infrastructure
As you might have seen, we occasionally get "too many connections" problems on drupal.org. During peak hours the load of the machine occasionally spikes to 10+. After such a burst, the load drops back below 2-3. Most of the day, the load is just below 1 though. I haven't investigated the problem yet but I figured I would let you know. For a few days now, I tried to get hold of Kjartan who administers the machine. It looks like he is traveling so I hope he gets back to us shortly. Know that we haven't properly configured the machine yet (it uses all the default settings) so chances are we get a long way by properly tuning the various configuration parameters. In fact, I don't even know whether we have PHP cache/optimizing installed. Clearly, we will have to look into that ASAP. -- Dries Buytaert :: http://www.buytaert.net/
There are some big gains you can get from just some simple apache/mysql config tweaks... also an opcode cacher makes a big difference (though we've been seeing some segfaults in eaccelerator lately :( Even just upping apache + mysql's max connection settings would probably be a good start. j On 19-Apr-05, at 2:39 AM, Dries Buytaert wrote:
As you might have seen, we occasionally get "too many connections" problems on drupal.org. During peak hours the load of the machine occasionally spikes to 10+. After such a burst, the load drops back below 2-3. Most of the day, the load is just below 1 though.
I haven't investigated the problem yet but I figured I would let you know. For a few days now, I tried to get hold of Kjartan who administers the machine. It looks like he is traveling so I hope he gets back to us shortly.
Know that we haven't properly configured the machine yet (it uses all the default settings) so chances are we get a long way by properly tuning the various configuration parameters. In fact, I don't even know whether we have PHP cache/optimizing installed. Clearly, we will have to look into that ASAP.
-- Dries Buytaert :: http://www.buytaert.net/
-- James Walker :: http://www.walkah.net/
On Tue, 19 Apr 2005, Karoly Negyesi wrote:
Even just upping apache + mysql's max connection settings would probably be a good start.
I think mysql thread caching helps, too.
Here's a link that Morbus sent me: http://jeremy.zawodny.com/blog/archives/000173.html Cheers, Gerhard
Status update: Kjartan just made some first configuration changes. We don't have a PHP cache/optimizer installed but that is on the TODO list. I'll keep you posted. On 19 Apr 2005, at 08:39, Dries Buytaert wrote:
As you might have seen, we occasionally get "too many connections" problems on drupal.org. During peak hours the load of the machine occasionally spikes to 10+. After such a burst, the load drops back below 2-3. Most of the day, the load is just below 1 though.
I haven't investigated the problem yet but I figured I would let you know. For a few days now, I tried to get hold of Kjartan who administers the machine. It looks like he is traveling so I hope he gets back to us shortly.
Know that we haven't properly configured the machine yet (it uses all the default settings) so chances are we get a long way by properly tuning the various configuration parameters. In fact, I don't even know whether we have PHP cache/optimizing installed. Clearly, we will have to look into that ASAP.
-- Dries Buytaert :: http://www.buytaert.net/
Another status update from the infrastructure department: Kjartan upgraded PHP to the latest version, tweaked the MySQL configuration, and installed a PHP optimizer/cache. As I type this, the machine's load is 0.67 but that might change when the US wakes up. On 19 Apr 2005, at 23:08, Dries Buytaert wrote:
Status update: Kjartan just made some first configuration changes. We don't have a PHP cache/optimizer installed but that is on the TODO list. I'll keep you posted.
On 19 Apr 2005, at 08:39, Dries Buytaert wrote:
As you might have seen, we occasionally get "too many connections" problems on drupal.org. During peak hours the load of the machine occasionally spikes to 10+. After such a burst, the load drops back below 2-3. Most of the day, the load is just below 1 though.
I haven't investigated the problem yet but I figured I would let you know. For a few days now, I tried to get hold of Kjartan who administers the machine. It looks like he is traveling so I hope he gets back to us shortly.
Know that we haven't properly configured the machine yet (it uses all the default settings) so chances are we get a long way by properly tuning the various configuration parameters. In fact, I don't even know whether we have PHP cache/optimizing installed. Clearly, we will have to look into that ASAP.
-- Dries Buytaert :: http://www.buytaert.net/
And hopefully the last update for a while: I announced the Drupal 4.6.0 release at Freshmeat.net today (during the peak hours) and the server remained crispy. To give you an idea, we are currently at 17k unique visitors a day (125k pages/day, 540k hits/day). PS: we're also compiling a list of slow queries. More about that later. On 20 Apr 2005, at 13:01, Dries Buytaert wrote:
Another status update from the infrastructure department:
Kjartan upgraded PHP to the latest version, tweaked the MySQL configuration, and installed a PHP optimizer/cache. As I type this, the machine's load is 0.67 but that might change when the US wakes up.
On 19 Apr 2005, at 23:08, Dries Buytaert wrote:
Status update: Kjartan just made some first configuration changes. We don't have a PHP cache/optimizer installed but that is on the TODO list. I'll keep you posted.
-- Dries Buytaert :: http://www.buytaert.net/
As you might have seen, we occasionally get "too many connections" problems on drupal.org. During peak hours the load of the machine occasionally spikes to 10+. After such a burst, the load drops back below 2-3. Most of the day, the load is just below 1 though.
I haven't investigated the problem yet but I figured I would let you know. For a few days now, I tried to get hold of Kjartan who administers the machine. It looks like he is traveling so I hope he gets back to us shortly.
Know that we haven't properly configured the machine yet (it uses all the default settings) so chances are we get a long way by properly tuning the various configuration parameters. In fact, I don't even know whether we have PHP cache/optimizing installed. Clearly, we will have to look into that ASAP.
1. It is worth installing eaccelerator, it speeds up request serving. We use it. 2. It would be a good idea to ditch the die(mysql_error()) now and replace it with a user friendly error page, don't you think. I proposed a patch before, and others also done that, although with different information exposure for the viewer. I think a simple dumb user oriented page should be displayed [1], but jhriggs thinks differently [2]. [1] http://drupal.org/node/8143 [2] http://drupal.org/node/9316 Please consider either the developer or the user friendly path, and voice your opinion on the need to update either one. Goba
participants (5)
-
Dries Buytaert -
Gabor Hojtsy -
Gerhard Killesreiter -
James Walker -
Karoly Negyesi