The OpenEdge Hive

phpMyAdmin shows, in its status view, several values that indicate bad index usage.

I have now added an index on table og_uid, on fields (uid,nid).
This table belongs to the OG module which is not a default Drupal module, which confirms my earlier suspicion.

It seems like a good idea to analyze many more queries, especially in the OG module first and then in other non-default modules.

Offline, Jurjen and I were discussing whether the SIFR headers have an impact on performance. He removed them in staging, and asked if I thought staging was any faster than live. My reply:

It's hard to say. The response times are so wildly variable that it's hard to get a feel for whether one is faster than the other.

I do notice that the SIFR headers appear about a half second after the browser (Opera) is done downloading and displaying the rest of the page contents.

We could try clobbering the SIFR (except for the SiteName) in live for now, and see how we like it.

This is the response I received from WestHost:

I have tested 4 pages on this account over the last 4 days. The average load time was 2.02 seconds. The server was within acceptable ranges. The apache benchmark tests I ran which excluded any network traffic issues, testing the responsivness of the server was very fast. All results of my tests are below.

Average = 2.02

Feb 26
URL:  http://oehive.org/
Measured Speed (using 10 mbps T3 connection): 1.64 sec

URL:  http://www.oehive.org/taxonomy/term/131/
Measured Speed (using 10 mbps T3 connection): 1.72 sec

URL:  http://www.oehive.org/taxonomy/term/214/
Measured Speed (using 10 mbps T3 connection): 2.61 sec

URL:  http://www.oehive.org/taxonomy/term/128/
Measured Speed (using 10 mbps T3 connection): 1.41 sec


Feb 25th
URL:  http://oehive.org/
Measured Speed (using 10 mbps T3 connection): 2.09 sec

URL:  http://www.oehive.org/taxonomy/term/131/
Measured Speed (using 10 mbps T3 connection): 2.36 sec

URL:  http://www.oehive.org/taxonomy/term/214/
Measured Speed (using 10 mbps T3 connection): 2.08 sec

URL:  http://www.oehive.org/taxonomy/term/128/
Measured Speed (using 10 mbps T3 connection): 2.14 sec


Febuary 24rth

Speed test results:
URL:  http://oehive.org
Measured Speed (using 10 mbps T3 connection): 3.09 sec

URL:  http://www.oehive.org/taxonomy/term/214
Measured Speed (using 10 mbps T3 connection): 1.88 sec

Speed test results:
URL:  http://www.oehive.org/taxonomy/term/131
Measured Speed (using 10 mbps T3 connection): 1.84 sec

Speed test results:
URL:  http://www.oehive.org/taxonomy/term/128
Measured Speed (using 10 mbps T3 connection): 1.41 sec


$ ab -n20 http://oehive.org/
This is ApacheBench, Version 1.3d <$Revision: 1.67 $> apache-1.3
Copyright (c) 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Copyright (c) 1998-2002 The Apache Software Foundation, http://www.apache.org/

Benchmarking oehive.org (be patient).....done
Server Software:        Apache/1.3.27
Server Hostname:        oehive.org
Server Port:            80

Document Path:          /
Document Length:        297 bytes

Concurrency Level:      1
Time taken for tests:   0.032 seconds
Complete requests:      20
Failed requests:        0
Broken pipe errors:     0
Non-2xx responses:      20
Total transferred:      10460 bytes
HTML transferred:       5940 bytes
Requests per second:    625.00 [#/sec] (mean)
Time per request:       1.60 [ms] (mean)
Time per request:       1.60 [ms] (mean, across all concurrent requests)
Transfer rate:          326.88 [Kbytes/sec] received

Connnection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0     0    0.0      0     1
Processing:     1     1    0.0      1     1
Waiting:        0     1    0.0      1     1
Total:          1     1    0.0      1     2

Hi Tim,

We use Drupal with page caching enabled. Because the same page seems to sometimes load fast and other times load slow, I don't think Drupal is to blame.

We use WestHost with a virtual private server. (With zero budget, that was all I was willing to go out-of-pocket for.) I agree that sometimes there is a 5 second page load time, and it is not acceptable. I'll send a complaint to WestHost.

Cheers,
John