Deprecated - Performance and scalability

site5 says it allows a maximum of 200 simultaneous mysql connections. how many signed in visitors would that translate into?

The company I work for has two main sites, one in Hawaii, the other in Chile.

We currently are hosting out of our Hawaii site. Because of the long distance, users in Chile have never been happy with server response time. We are planning on upgrading our sun hardware to opteron or niagara. We want to reuse the older hardware with the new stuff in conjuction with a load-balancer.

Through Bryght, I’ve been working on an interesting project that really exercises the “toolkit” and “web services platform” like nature of Drupal. The final architecture of our project ended up having many distributed processes, all sending data to Drupal through XML-RPC, and we were using Drupal mainly to aggregate and display the results.

Performance was very important, and we were having a huge bottle neck with Drupal’s XML-RPC library. XML-RPC calls were talking a long fricken time, and we were making tons of them.

Fortunately I had help from Walkah and Moshe, and I thought I would pass on what we did to drastically increase XML-RPC performance. This worked for us, so maybe it might help someone else out.

The problem is of course that Drupal does a full bootstrap for every XML-RPC call.

Our solution:
The first, simple (and huge) win was to utilize a PHP opcode cacher - this drastically reduces this bootstrapping time. We used eAccelerator, but there are many others.

Secondly, since we were working in a controlled environment (we knew what modules were going to be called via XML-RPC) we were able to hack the xmlrpc.php file to avoid a full bootstrap. The downside is we had to hardcode a few path variables into the file, but again, this is for a particular app/site, and the performance gains were worth it.

Courtesy of Moshe, here is our revised xmlrpc.php file that doesn't do a full bootstrap and only loads the database layer. You might want to rename your xmlrpc.php file to xmlrpcs.php or something...

Hi All,

Hi,
I saw this in another script and was wandering if it would ever been considered for a future drupal:

on any template a "cache begin" / "cache end" can be put arround any number of individual dynamic code, each with a setting of cache duration. When the page is called from a browser, the dynamic code is replaced by a simple call to a static file.

First, create the node (content type) named “test” and in the menu(access control), click the “create test content” check box and click the “edit test content” check box.
So, normally for the administrator level, they can create and edit all the new created contents because they have full authority.
But for the users, like authenticated users, they can’t edit their new contents even they are given to edit permission.