pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Kefan Yang <starordust@gmail.com>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: alvherre@2ndquadrant.com <alvherre@2ndquadrant.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: RE: GSOC 2018 Project - A New Sorting Routine
Date: Mon, 30 Jul 2018 14:21:15 -0700
Message-ID: <5b5f8149.1c69fb81.e06c6.d054@mx.google.com> (raw)
In-Reply-To: <fbfd760c-2c6d-e38d-86dc-c58b8b0304e3@2ndquadrant.com>
References: <CAF448YLZz5cD+w5qYQGMcfFPY9zAu2mkkiCtOPSBJmwbjuPNig@mail.gmail.com>
	<57ae7691-6dc8-d6d0-361a-a7269e656273@2ndquadrant.com>
	<CAF448YKLbmmSPbb_AFEaTKozjnFOEfT+s2eiSjfH=us34VNr4w@mail.gmail.com>
	<CAF448YK0xhqK6mg3EeP-dt4j9V-VxkG8Vswmrt3t90OYSrNSsQ@mail.gmail.com>
	<CAH2-Wzmj2XstMK58tJ0yEr+0MwpqMU8rfUB0j7GVe=p+yW5rTg@mail.gmail.com>
	<00147235-69d3-d4f0-36c1-198d630af7ad@2ndquadrant.com>
	<1C5B17F1-D37F-4730-A2E4-EB7288C6DC09@yandex-team.ru>
	<78b9c822-e127-5250-a01c-4c51a50c82bd@2ndquadrant.com>
	<5b4fad82.1c69fb81.7a6f6.d32b@mx.google.com>
	<58417882-04e3-b23e-b53e-7d0720558335@2ndquadrant.com>
	<5b5654cc.1c69fb81.5ea44.d698@mx.google.com>
	<fbfd760c-2c6d-e38d-86dc-c58b8b0304e3@2ndquadrant.com>

Hey Tomas! 

Sorry to bother but it would be great if we can get the test results this week.

Regards,
Kefan

From: Tomas Vondra
Sent: July 24, 2018 8:16 AM
To: Kefan Yang
Cc: Andrey Borodin; Peter Geoghegan; alvherre@2ndquadrant.com; PostgreSQL Hackers
Subject: Re: GSOC 2018 Project - A New Sorting Routine



On 07/24/2018 12:21 AM, Kefan Yang wrote:
> Hi Tomas!
> 
> I did a few tests on my own Linux machine, but the problem is that my 
> resources on AWS(CPU, RAM and even Disk space) are very limited. I 
> considered establishing virtual machine on my own PC but the performance 
> is even worse.
> 
> My original patch has two main optimizations: (1) switch to heap sort 
> when depth limit exceeded (2) check whether the array is presorted only 
> once at the beginning. Now I want to test these optimizations 
> separately. On AWS EC2 instance, regressions on CREATE INDEX cases seems 
> to be less significant if we use (1) only, but I can only test up to 
> 100000 records and 512MB memory using your scripts.
> 
> So would you mind re-running the tests using the two patches I provided 
> in the attachment? That will be very helpful
> 

I can do that, but it'll have to wait a couple of days. I'm currently 
using the boxes for some other tests.

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

view thread (15+ messages)  latest in thread

Message-ID: <5b5f8149.1c69fb81.e06c6.d054@mx.google.com>
Permalink:  ../5b5f8149.1c69fb81.e06c6.d054@mx.google.com/
Also on:    postgresql.org/message-id/5b5f8149.1c69fb81.e06c6.d054@mx.google.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: starordust@gmail.com, tomas.vondra@2ndquadrant.com, x4mmm@yandex-team.ru, pg@bowt.ie, alvherre@2ndquadrant.com, pgsql-hackers@lists.postgresql.org
  Subject: RE: GSOC 2018 Project - A New Sorting Routine
  In-Reply-To: <5b5f8149.1c69fb81.e06c6.d054@mx.google.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox