Hi Yanrui:
On Wed, Nov 19, 2014 at 2:48 AM, Yanrui Hu wrote:
> I am partly understanding your explain.
>
Enough for me, it isn't a simple thing to write :)
> the "including connection establish" case means the db connection not only
> socket connection, the "excluding connection establish" ca
On 11/18/2014 9:36 PM, Yanrui Hu wrote:
What I would like to know is how much the network changed impact on
the tps changes in two cases.
you just measured that.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-gene
On 11/18/2014 5:48 PM, Yanrui Hu wrote:
Based on your mail, my senario is more like "excluding connection
establish" case, right? So the network change make the capacity
decrease to 1/5 (204->42). The network change impact the system so much!
have you measured the packet latency, with ping o
Adrian,
I understand you about the tps explain.
What I would like to know is how much the network changed impact on the tps
changes in two cases.
On Wed, Nov 19, 2014 at 10:58 AM, Adrian Klaver
wrote:
> On 11/18/2014 05:53 PM, Yanrui Hu wrote:
>
>> Adrian,
>> I saw that in two case, one is 5450
On 11/18/2014 05:53 PM, Yanrui Hu wrote:
Adrian,
I saw that in two case, one is 54502 transactions and the other is 13966
but that is caused by capacity decrease.
And fps is transaction per second, so it's not the transactions but
transaction per second, so I don't think the total transactions
di
Adrian,
I saw that in two case, one is 54502 transactions and the other is 13966
but that is caused by capacity decrease.
And fps is transaction per second, so it's not the transactions but
transaction per second, so I don't think the total transactions different
has any problem.
Please point if my
Thanks Francisco,
I am partly understanding your explain.
the "including connection establish" case means the db connection not only
socket connection, the "excluding connection establish" case include many
db query and more depends on socket latency, right?
And what's your suggestion on my testing
On 11/18/2014 12:33 AM, Yanrui Hu wrote:
I am working on a evaluation to put db client outside the datacenter and
to know how the network impact on the business.
After several round of testing, I have a question regarding to the two
tps result in stress output.
Test A:
Client and DB server exist
Hi Yanrui:
On Tue, Nov 18, 2014 at 10:46 AM, Yanrui Hu wrote:
> It the "connection establishing" means socket connect? If so, that 's the
> only different for my case A and B.
> So the result of "exclude connection establishing" should be similar,
> right?
>
When you connect to the database you
It the "connection establishing" means socket connect? If so, that 's the
only different for my case A and B.
So the result of "exclude connection establishing" should be similar, right?
My overall test is to fingure out the what's the impact if my client access
db server from out side datacenter(
On 11/18/2014 12:33 AM, Yanrui Hu wrote:
the tps excluding connections establishing should be very close,
right? Because the database is same and capability is same only
network latency is different.
that greatly latency is added to every sql command you send and get
results from. why would
I am working on a evaluation to put db client outside the datacenter and to
know how the network impact on the business.
After several round of testing, I have a question regarding to the two tps
result in stress output.
Test A:
Client and DB server exist in same AWS datacenter.
transaction type:
12 matches
Mail list logo
