Re: Incoming/Sent traffic data - Mailing list pgsql-jdbc

From Israel Ben Guilherme Fonseca
Subject Re: Incoming/Sent traffic data
Date
Msg-id BANLkTindHFPiB6SMpFKyF2f981STAV84Uw@mail.gmail.com
Whole thread Raw
In response to Re: Incoming/Sent traffic data  (Maciek Sakrejda <msakrejda@truviso.com>)
Responses Re: Incoming/Sent traffic data
List pgsql-jdbc
I just got a try with the wireshark, it's indeed nice, but I didn't figure a good filter for knowing what's my app trafic (I'm on localhost), so I put the 'lo' interface, executed the test, pick some random package that have just been collected, get the source port (the application port that's random), and filter packages that use it.

I did a fast test with both languages and it's still look that the Java traffic is somewhat bigger. (I couldn't isolate the setup traffic)

Total Traffic (same test of before but the select is in a loop of 20 iterations)
28KB python
39KB java

The strange thing is, I compared the results of my proxy and wireshark for the Java test, and it's ok. For the python test, there was a difference of 10KB between the proxy and wireshark result. I dunno why. I'll have to explore this a bit more.

Do you have experience with this Macieck? Could I sent direct email to you regarding the wireshark questions?

2011/5/12 Maciek Sakrejda <msakrejda@truviso.com>
> About the log, i'm using log_statement = "all", on the postgres config,is there any
> other specific option?

You could try setting log_min_messages = debug1 (I don't think
anything below that--i.e., debug2 through debug5--is useful for your
case, but you can give it a shot to see what's there).

> My current implementation of proxy just use sockets to transmit the data between the app (that's
> why the port 4444 on connections) to the database, that's how I check the size of data
> transfered with it (it have a GUI to clear the traffic so I can check only the operation, not the
> setup).

Nice. I didn't mean to imply you were entirely unscientific about
this, just that you should be careful regarding assumptions as to what
is sent where when. A tool like Wireshark is (relatively) easy to pick
up and gives you tremendous insight into what's going on on the wire
with no application changes required (and it even has a PostgreSQL
protocol plugin by default so you don't need to stare at raw bytes).

---
Maciek Sakrejda | System Architect | Truviso

1065 E. Hillsdale Blvd., Suite 215
Foster City, CA 94404
(650) 242-3500 Main
www.truviso.com

pgsql-jdbc by date:

Previous
From: Maciek Sakrejda
Date:
Subject: Re: Incoming/Sent traffic data
Next
From: Samuel Gendler
Date:
Subject: Re: Incoming/Sent traffic data