In the document, we installed one coordinator and one data node into
one physical server to make best user of both coordinators and data
nodes, independent from the workload shared by coordinators and data
nodes.
It also make parameters simple to claim the sacalability against the
number of servers involved. I don't thinks it's a good idea to
install loader and coordinator in the same server. Loader's work is
simply application-oriented and should not be included as a part of
database performance.
As Mason mentioned, I'm very interested in the spec of servers, number
of servers used and configuration information what components (GTM,
coordinators and data nodes) you installed in what servers, as well as
network connections.
As you might have seen, we need gigabit network links between GTM,
Coordinators and Data Nodes. I strongly recommend to use good L2
switch to reduce the network worklord too.
Kind Regards;
----------
Koichi Suzuki
2010/11/23 Mason Sharp <mas...@en...>:
> On 11/23/10 3:27 AM, xiong wang wrote:
>> Dears,
>>
>> I tested the postgres-xc DBT1 performance according to the published
>> document. But the result is worse than what the document declares. One
>> loader with one coordinator is much better. One loader with two
>> coordinators is much worse than the former. I don't know which way is
>> right. And I don't know the reason why the latter method is so worse
>> than the former.
>>
>>
> How much worse?
>
> How many physical servers are in each configuration? How is each server
> configured in each, with how many data nodes? What kind of network?
> Gigabit?
>
> Or was everything on one system? With virtual machines or without and
> just using different ports?
>
> Are there errors in the log file (connection limits hit)?
>
> Regards,
>
> Mason
>
>> You reply will be appreciated.
>>
>> Thanks.
>>
>> Best regards,
>>
>> Benny
>>
>> ------------------------------------------------------------------------------
>> Increase Visibility of Your 3D Game App& Earn a Chance To Win $500!
>> Tap into the largest installed PC base& get more eyes on your game by
>> optimizing for Intel(R) Graphics Technology. Get started today with the
>> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
>> http://p.sf.net/sfu/intelisp-dev2dev
>> _______________________________________________
>> Postgres-xc-developers mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>>
>
>
> --
> Mason Sharp
> EnterpriseDB Corporation
> The Enterprise Postgres Company
>
>
> This e-mail message (and any attachment) is intended for the use of
> the individual or entity to whom it is addressed. This message
> contains information from EnterpriseDB Corporation that may be
> privileged, confidential, or exempt from disclosure under applicable
> law. If you are not the intended recipient or authorized to receive
> this for the intended recipient, any use, dissemination, distribution,
> retention, archiving, or copying of this communication is strictly
> prohibited. If you have received this e-mail in error, please notify
> the sender immediately by reply e-mail and delete this message.
>
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> Postgres-xc-developers mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postgres-xc-developers
>
|
