Re: [Postgres-xc-general] Postgresql - Postgres-XC

Hi Iwan,

We don't want want to discourage you from using XC.  Just give your self
enough time to test where you can simulate the workload that you experience
in production.  If you can partition/distribute your tables cleanly such
that all joins always take place locally, XC should help you. If that is
not the case, XC will resort to shipping a lot of data to a single
coordinator to join. So, you may notice that most operations seem to scale,
but a handful of statements now take several minutes or more (something we
have addressed in StormDB's fork of XC).

As the others have said, you could look at tuning standard PG first,
looking at shared_buffers, work_mem, etc., moving WAL off to its own disk.
You may want to also log long queries by setting log_min_duration_statement
to a couple of seconds (perhaps less) and see if any particular statement
is slow due to a missing index or untuned parameters.



On Mon, Dec 31, 2012 at 7:47 AM, Iwan Sofana <iwa...@ya...> wrote:

> **
> At peek hour is about 1000 transaction per second, and the aggregates run
> over 1250000 rows, possibly will increase again.
> Send by Ojolinux
> ------------------------------
> *From: * Jim Mlodgenski <ji...@gm...>
> *Date: *Sun, 30 Dec 2012 10:39:55 -0500
> *To: *Iwan Sofana<iwa...@ya...>
> *Cc: *<pos...@li...>
> *Subject: *Re: [Postgres-xc-general] Postgresql - Postgres-XC
>
>
>
> On Sun, Dec 30, 2012 at 10:01 AM, Iwan Sofana <iwa...@ya...>wrote:
>
>> I am glade to hear that.
>>
>>
>> > The limit to a single table in PostgreSQL is 32TB so 800GB is still
>> only a moderately sized database.
>>
>> Hundred users from different area can access application and insert
>> data.
>> The application doing math calculation (average, sum, min, max) and store
>> the result in several tables.
>>
>
> About how many transactions per second are you seeing? 100, 1000, 10000?
> The aggregates (average, sum) are run over how many rows? 1000, 1 million,
> 100 million?
>
>
>>
>> > What is the application doing to produce such a high CPU load? Is it
>> many concurrent users? A lot of large sorts? etc?
>>
>> > Understanding why the CPU is high will help determine if XC is the
>> right solution to solve your problem. It could be that some simple tuning
>> or database maintenance could reduce the CPU load and delay your need to
>> move beyond a single server.
>>
>
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. SALE $99.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122412
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>
>


-- 
Mason Sharp

StormDB - http://www.stormdb.com
The Database Cloud
Postgres-XC Support and Services