What O/S or hardware feature would be useful for databases?

From: Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>
To: pgsql-general(at)postgresql(dot)org
Subject: What O/S or hardware feature would be useful for databases?
Date: 2007-06-16 15:47:02
Message-ID: 200706161549.l5GFnqfL000993@smtp2.jaring.my
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

I've been wondering, what O/S or hardware feature would be useful for
databases?

If Postgresql developers could get the CPU and O/S makers to do
things that would make certain things easier/faster (and in the long
term) what would they be?

By long term I mean it's not something that's only useful for a few
years. Not something "gimmicky".

For example - something like virtual memory definitely made many
things easier. Hardware support for virtualization also makes stuff
like vmware easier and better.

Seems CPU makers currently have more transistors than they know what
to do with, so they're adding cores and doing a lot of boring stuff
like SSE2, SSE3, SSE4, etc.

So is there anything else useful that they (and the O/S ppl) can do
that they aren't doing already?

Better support for distributed locking (across cluster nodes etc)? OK
that's old stuff, but the last I checked HP was burying VMS and Tandem.

Hardware acceleration for quickly counting the number of
set/unset/matching bits?

Regards,
Link.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gregory Stark 2007-06-16 15:54:59 Re: Using the GPU
Previous Message PFC 2007-06-16 15:46:25 Re: persistent db connections in PHP