Re: Drupal and PostgreSQL - performance issues?
От | Mikkel Høgh |
---|---|
Тема | Re: Drupal and PostgreSQL - performance issues? |
Дата | |
Msg-id | ABC43831-1DB5-4AF3-AAD5-E6A607B6AE34@hoegh.org обсуждение исходный текст |
Ответ на | Re: Drupal and PostgreSQL - performance issues? (Ivan Sergio Borgonovo <mail@webthatworks.it>) |
Ответы |
benchmark on D7 + PG 8.3 Re: Drupal and PostgreSQL -
performance issues?
|
Список | pgsql-general |
Hmm, those are interesting numbers. Did you use a real, logged in, drupal session ID (anonymous users also get one, which still gives them cached pages). They are in the form of "SESS6df8919ff2bffc5de8bcf0ad65f9dc0f=59f68e60a120de47c2cb5c98b010ffff" Note how the thoughput stays in the 30-ish range from 100 to 400, although the response time climbs steeply. That might indicate that your Apache configuration is the main roadblock here, since that indicates that clients are waiting for a free Apache process to handle their request (I suppose you're using MPM_PREFORK)… -- Kind regards, Mikkel Høgh <mikkel@hoegh.org> On 14/10/2008, at 18.44, Ivan Sergio Borgonovo wrote: > BTW I hope someone may find good use of this: > > 2xXeon HT CPU 3.20GHz (not dual core), 4Gb RAM, RAID 5 SCSI > * absolutely not tuned Apache > * absolutely not tuned Drupal with little content, some blocks and > some google adds > (just CSS aggregation and caching enabled) > * lightly tuned PostgreSQL 8.1 > shared_buffers = 3500 > work_mem = 32768 > checkpoint_segments = 10 > effective_cache_size = 15000 > random_page_cost = 3 > default_statistics_target = 30 > > siege -H "Cookie: drupalsessid" -c1 "localhost/d1" > -b -t30s > > -c 1 > Transactions: 485 hits > Availability: 100.00 % > Elapsed time: 29.95 secs > Data transferred: 5.33 MB > Response time: 0.06 secs > Transaction rate: 16.19 trans/sec > Throughput: 0.18 MB/sec > Concurrency: 1.00 > Successful transactions: 485 > Failed transactions: 0 > Longest transaction: 0.13 > Shortest transaction: 0.06 > > -c 5 > Transactions: 1017 hits > Availability: 100.00 % > Elapsed time: 29.61 secs > Data transferred: 11.29 MB > Response time: 0.15 secs > Transaction rate: 34.35 trans/sec > Throughput: 0.38 MB/sec > Concurrency: 4.98 > Successful transactions: 1017 > Failed transactions: 0 > Longest transaction: 0.24 > Shortest transaction: 0.08 > > -c 20 > Transactions: 999 hits > Availability: 100.00 % > Elapsed time: 30.11 secs > Data transferred: 11.08 MB > Response time: 0.60 secs > Transaction rate: 33.18 trans/sec > Throughput: 0.37 MB/sec > Concurrency: 19.75 > Successful transactions: 999 > Failed transactions: 0 > Longest transaction: 1.21 > Shortest transaction: 0.10 > > -c 100 > Transactions: 1085 hits > Availability: 100.00 % > Elapsed time: 29.97 secs > Data transferred: 9.61 MB > Response time: 2.54 secs > Transaction rate: 36.20 trans/sec > Throughput: 0.32 MB/sec > Concurrency: 91.97 > Successful transactions: 911 > Failed transactions: 0 > Longest transaction: 12.41 > Shortest transaction: 0.07 > > -c 200 > Transactions: 1116 hits > Availability: 100.00 % > Elapsed time: 30.02 secs > Data transferred: 9.10 MB > Response time: 4.85 secs > Transaction rate: 37.18 trans/sec > Throughput: 0.30 MB/sec > Concurrency: 180.43 > Successful transactions: 852 > Failed transactions: 0 > Longest transaction: 15.85 > Shortest transaction: 0.25 > > -c 400 > Transactions: 1133 hits > Availability: 100.00 % > Elapsed time: 29.76 secs > Data transferred: 8.51 MB > Response time: 6.98 secs > Transaction rate: 38.07 trans/sec > Throughput: 0.29 MB/sec > Concurrency: 265.85 > Successful transactions: 736 > Failed transactions: 0 > Longest transaction: 28.55 > Shortest transaction: 0.00
Вложения
В списке pgsql-general по дате отправления:
Следующее
От: Stephen FrostДата:
Сообщение: Re: Why select 1 where current_date = 'infinity'; doesn't work?