Re: quad or dual core Intel CPUs

Поиск
Список
Период
Сортировка
От Kenji Morishige
Тема Re: quad or dual core Intel CPUs
Дата
Msg-id 20070214172501.GA2405@juniper.net
обсуждение исходный текст
Ответ на Re: quad or dual core Intel CPUs  ("Claus Guttesen" <kometen@gmail.com>)
Ответы Re: quad or dual core Intel CPUs
Список pgsql-performance
Thanks Claus thats good news!
I'm having a reputable vendor build the box and test it for me before
delivering.  The bottom line of your message, did you mean 'should be not a
problem'?  I wonder what the main reason for your improvement, your ram was
increased by a factor of 2, but 4 way opteron vs 4 way woodcrest performance
must not be that significant.

-Kenji


> We recently migrated from a four way opteron @ 2 GHz with 8 GB to a
> four way woodcrest @ 3 GHz (HP DL380 G5) with 16 GB ram. I also
> upgraded FreeBSD from 6.0 to 6.2 and did a minor upgrade of postgresql
> from 7.4.9 to 7.4.12. The change was tremendous, the first few hours
> of after it went into production I had to doublecheck that our website
> worked, since the load was way below 1 whereas the load had been
> almost 100 during peak.
>
> I don't have any financial ties to HP but building a server from
> scratch may not be worth it, rather than spending time assemling all
> the different parts yourself I would suggest you get a server from one
> vendor who build a server according to your specs.
>
> The DL380 (also) has a 256 MB bbc controller, the nic works flawlessly
> with FreeBSD 6.2, all parts are well integrated, the frontbay can
> accomodate 8 146 GB SAS drives. This server is wellsuited as a
> postgresql-server.
>
> Approx. 200 reqest a sec. should be a problem unless the queries are heavy.
>
> regards
> Claus

В списке pgsql-performance по дате отправления:

Предыдущее
От: Mark Stosberg
Дата:
Сообщение: reindex vs 'analyze' (was: Re: cube operations slower than geo_distance() on production server)
Следующее
От: Tom Lane
Дата:
Сообщение: Re: reindex vs 'analyze' (was: Re: cube operations slower than geo_distance() on production server)