On Thu, Jun 23, 2011 at 5:01 AM, Radosław Smogura
wrote:
> I think conclusion from this test was "Much more important things are to do,
> then 1% benefit" - not "1% is worthless".
>
> I will try today hugepages, with random peeks.
I think the real conclusion here is "Linux will soon do this for u
Martijn van Oosterhout Thursday 23 of June 2011 09:10:20
> On Wed, Jun 22, 2011 at 02:31:01PM +0200, Rados??aw Smogura wrote:
> > I strictly disagree with opinion if there is 1% it's worthless. 1%
> > here, 1% there, and finally You get 10%, but of course hugepages
> > will work quite well if will
On Wed, Jun 22, 2011 at 02:31:01PM +0200, Rados??aw Smogura wrote:
> I strictly disagree with opinion if there is 1% it's worthless. 1%
> here, 1% there, and finally You get 10%, but of course hugepages
> will work quite well if will be used in code that require many
> random "jumps". I think this
On Wed, 22 Jun 2011 14:24:17 +0300, Marti Raudsepp wrote:
On Sun, Jun 19, 2011 at 12:56, Radosław Smogura
wrote:
I want to implement hugepages for shared memory
Hi,
Have you read this post by Tom Lane about the performance estimation
and a proof-of-concept patch with hugepages?
http://archiv
On Sun, Jun 19, 2011 at 12:56, Radosław Smogura
wrote:
> I want to implement hugepages for shared memory
Hi,
Have you read this post by Tom Lane about the performance estimation
and a proof-of-concept patch with hugepages?
http://archives.postgresql.org/pgsql-hackers/2010-11/msg01842.php
It's p
Martijn van Oosterhout writes:
> On Sun, Jun 19, 2011 at 11:56:15AM +0200, Rados??aw Smogura wrote:
>> I want to implement hugepages for shared memory, to make it transparent I
>> want
> At least in Linux they're trying to make hugepages transparent, so I'm
> wondering if this is going to make
Martijn van Oosterhout Sunday 19 of June 2011 12:35:18
> On Sun, Jun 19, 2011 at 11:56:15AM +0200, Rados??aw Smogura wrote:
> > I want to implement hugepages for shared memory, to make it transparent I
> > want to do in this fashion:
> > 1. Reserve memory M of size s
> > 2. Try to allocate hugepag
On Sun, Jun 19, 2011 at 11:56:15AM +0200, Rados??aw Smogura wrote:
> I want to implement hugepages for shared memory, to make it transparent I
> want
> to do in this fashion:
> 1. Reserve memory M of size s
> 2. Try to allocate hugepage memory of as big size as possible (hs), attach at
> M.
> 3.
I want to implement hugepages for shared memory, to make it transparent I want
to do in this fashion:
1. Reserve memory M of size s
2. Try to allocate hugepage memory of as big size as possible (hs), attach at
M.
3. Allocate normal shared memory of size hs - s, and attach it at M+hs.
This souluti
