From: | Blazej <bl(dot)oleszkiewicz(at)gmail(dot)com> |
---|---|
To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | avin_friends(at)yahoo(dot)com, "postgresql Forums" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: In memory Database for postgres |
Date: | 2008-11-17 23:31:50 |
Message-ID: | 819df3760811171531p5b8870c4m261b9c84cdf134de@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2008/11/18 Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>:
> On Mon, Nov 17, 2008 at 3:02 PM, Blazej <bl(dot)oleszkiewicz(at)gmail(dot)com> wrote:
>> In my opinion very nice solution is building part of PostgreSQL
>> database in memory - below it is instruction how to build PostgreSQL
>> schema in memory in Linux. I tested this with my ROLAP solution for
>> recalculation MOLAP cubes in memory and then join with master cube
>> (this speeds up proces about 10 times!!! - but in other solution may
>> be different).
>
> Just wondering if you compared it to how fast it runs if you've got
> lots of shared_buffers and everything fits into memory. That would be
> an interesting comparison.
>
They are two small thing becouse I do this how I have described above:
(1) shared_buffers is SHARED;
(2) I needed extremaly speed up so if table stored in hdd it must be
sync (sooner or later - even if sync is off), so this operation is
very slowly on hdd when it compares to ram_disk.
Regards,
Blazej
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2008-11-18 00:27:27 | Re: Res: Res: Archive files growth!!! |
Previous Message | Greg Smith | 2008-11-17 23:26:48 | Re: In memory Database for postgres |