Your patch is very helpful, I'm still checking it on different file-systems.
I really liked the idea of using only the edge checkpoints.
Thanks.
On Mon, Jul 11, 2016 at 9:26 PM, Jeff Janes wrote:
> On Thu, Jul 7, 2016 at 1:01 AM, Netanel Katzburg
> wrote:
> > Hi All,
> >
> > As part of my maste
On Thu, Jul 7, 2016 at 1:01 AM, Netanel Katzburg wrote:
> Hi All,
>
> As part of my masters at TAU, I'm currently conducting some research
> regarding new persistent memory technology.
> I'm using PG for this research and would like to better understand some of
> the performance bottlenecks.
> For
Hi,
You were right, the method you described worked well. Thanks you!
But so far, could not get any noticeable improvement in Number of
transactions / latency.
I have tried:
1. At xlog.c, CopyXLogRecordToWAL(int write_len, bool isLogSwitch,
XLogRecData *rdata,
XLogRecPtr StartPos, XLogRecPtr En
On 11 July 2016 at 19:14, Netanel Katzburg wrote:
> Hi,
>
> You were right, the method you described worked well. Thanks you!
>
> But so far, could not get any noticeable improvement in Number of
> transactions / latency.
>
>
What are you comparing to?
To start with, compare with:
- an unpatch
On 10 July 2016 at 18:27, Netanel Katzburg wrote:
> BUT, both options are not good, as they are stopping me from even running i
> *nitdb.*
>
>
>
The easiest path for testing will be to use an unpatched PostgreSQL to
`initdb` and create a new database. Then start up a patched one that simply
skip
Hi Michael,
Sorry for the delay,
The answer is yes,
I tried 2 things so far:
1. As I understand:
*XLogRecPtr*
*XLogInsert(RmgrId rmid, uint8 info)*
is the primary insert function in xloginsert.c.
I tried commenting the following line at this function, so I can return a
phony pointer every time
On Thu, Jul 7, 2016 at 5:01 PM, Netanel Katzburg wrote:
> 1. Disable the WAL by not writing anything to the xlog directory. I don't
> care about recovery/fault tolerance or PITR/ replication etc at the moment.
> I'm aware that the WAL and checkpoint are bind in many ways and are crucial
> for PG c
Hi All,
As part of my masters at TAU, I'm currently conducting some research
regarding new persistent memory technology.
I'm using PG for this research and would like to better understand some of
the performance bottlenecks.
For this reason I'm trying to disable the WAL completely, using some hack
