Yes!
Probably very much so. There is good evidence that using multiple CPU's and
GPU's will
speed sorting and many other database operations too.
See
http://www.cs.cmu.edu/afs/cs.cmu.edu/Web/People/ngm/15-823/project/Final.pdf
The question become how practical is it? There are numerous iss
j...@nasby.net (Jim Nasby) writes:
> On Dec 10, 2010, at 6:18 PM, Jeff Janes wrote:
>> On Fri, Dec 10, 2010 at 3:09 PM, Hamza Bin Sohail wrote:
>>>
>>> Hello hackers,
>>>
>>> I think i'm at the right place to ask this question.
>>>
>>> Based on your experience and the fact that you have written
On Dec 10, 2010, at 6:18 PM, Jeff Janes wrote:
> On Fri, Dec 10, 2010 at 3:09 PM, Hamza Bin Sohail wrote:
>>
>> Hello hackers,
>>
>> I think i'm at the right place to ask this question.
>>
>> Based on your experience and the fact that you have written the Postgres
>> code,
>> can you tell what
Thanks alot for all the replies. Very helpful, really appreciate it.
- Original Message -
From: "Jeff Janes"
To: "Hamza Bin Sohail"
Cc:
Sent: Friday, December 10, 2010 7:18 PM
Subject: Re: [HACKERS] would hw acceleration help postgres (databases in
general)
On Fri, Dec 10, 2010 at 3:09 PM, Hamza Bin Sohail wrote:
>
> Hello hackers,
>
> I think i'm at the right place to ask this question.
>
> Based on your experience and the fact that you have written the Postgres code,
> can you tell what a rough break-down - in your opinion - is for the time the
> d
On 12/10/10 3:09 PM, Hamza Bin Sohail wrote:
> There is not much utility in doing this if there aren't considerable compute-
> intensive operations in the database (which i would be surprise if true ). I
> would suspect joins, complex queries etc may be very compute-intensive.
> Please
> correc
> -Original Message-
> From: pgsql-hackers-ow...@postgresql.org [mailto:pgsql-hackers-
> ow...@postgresql.org] On Behalf Of Hamza Bin Sohail
> Sent: Friday, December 10, 2010 3:10 PM
> To: pgsql-hackers@postgresql.org
> Subject: [HACKERS] would hw acceleration help post
Hello hackers,
I think i'm at the right place to ask this question.
Based on your experience and the fact that you have written the Postgres code,
can you tell what a rough break-down - in your opinion - is for the time the
database spends time just "fetching and writing " stuff to memory and
