Re: [Postgres-xc-general] Looks like co-ordinator is my perf bottleneck....somebody help...

[Koichi S. <koi...@gm...>]

It is not a good way to replicate all the tables for write
scalability.   The best way is to distribute transaction tables (very
frequently written ones) and replicate master tables (less frequently
written and frequently joined with transaction tables).

Example is our DBT-1 benchmark.  Slide 12 of
http://postgres-xc.sourceforge.net/misc-docs/20120614_PGXC_Tutorial_global.pdf
shows how we designed DBT-1 table distribution for XC.  I hope this
helps.

Regards;
---
Koichi Suzuki


2014-02-01 Nirmal Sharma <sha...@gm...>:
> Hi,
>
> I created a pgxc cluster with one coordinator, one GTM and 6 data nodes (all
> on same big machine ).
> To test the performance, i ran one query through coordinator on my data
> which is evenly distributed on all the nodes and it took total 25 sec to
> complete.
>
> And then i ran the same query on datanodes directly and it took 5 sec on
> each and every datanodes.
>
> Since query execution happens parallely on data nodes so ideally even if i
> run the query through coordinator, it should not take more than 5-8 sec max
> but i dont understand why is it taking 25 sec.
>
> Can somebody help me.?
> Do i need to make some changes to my cluster configuration?
>
>
> Regards
> Nirmal
>
> ------------------------------------------------------------------------------
> WatchGuard Dimension instantly turns raw network data into actionable
> security intelligence. It gives you real-time visual feedback on key
> security issues and trends.  Skip the complicated setup - simply import
> a virtual appliance and go from zero to informed in seconds.
> http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
> _______________________________________________
> Postgres-xc-general mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-general
>