From: | Juan Casero <caseroj(at)comcast(dot)net> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | Fwd: PostgreSQL and Ultrasparc T1 |
Date: | 2005-12-18 17:20:44 |
Message-ID: | 200512181220.44837.caseroj@comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
I think maybe the postgresql developers would be able to provide some
insightful comments on this question. Forgive me if it is not strictly about
development.
Thanks,
Juan
---------- Forwarded Message ----------
Subject: PostgreSQL and Ultrasparc T1
Date: Sunday 18 December 2005 11:35
From: Juan Casero <caseroj(at)comcast(dot)net>
To: pgsql-performance(at)postgresql(dot)org
Hi -
Can anyone tell me how well PostgreSQL 8.x performs on the new Sun Ultrasparc
T1 processor and architecture on Solaris 10? I have a custom built retail
sales reporting that I developed using PostgreSQL 7.48 and PHP on a Fedora
Core 3 intel box. I want to scale this application upwards to handle a
database that might grow to a 100 GB. Our company is green mission conscious
now so I was hoping I could use that to convince management to consider a Sun
Ultrasparc T1 or T2 system provided that if I can get the best performance
out of it on PostgreSQL. So will newer versions of PostgreSQL (8.1.x) be
able to take of advantage of the multiple cores on a T1 or T2? I cannot
change the database and this will be a hard sell unless I can convince them
that the performance advantages are too good to pass up. The company is
moving in the Win32 direction and so I have to provide rock solid reasons for
why I want to use Solaris Sparc on a T1 or T2 server for this database
application instead of Windows on SQL Server.
Thanks,
Juan
-------------------------------------------------------
-------------------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-12-18 17:57:17 | Re: Fwd: PostgreSQL and Ultrasparc T1 |
Previous Message | User Gsmet | 2005-12-18 16:04:34 | pgfouine - pgfouine: fixed a missing reference |