| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Dmitri Girski <mitek17(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: pg_connect takes 3.0 seconds |
| Date: | 2010-01-07 03:34:56 |
| Message-ID: | dcc563d11001061934r1f220029v896ea63beae298e6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, Jan 6, 2010 at 7:44 PM, Dmitri Girski <mitek17(at)gmail(dot)com> wrote:
> Hi everybody,
> Many thanks to everyone replied, I think we are on the right way.
> I've used tcpdump to generate the logs and there are a lot of dropped
> packets due to the bad checksum. Network guy is currently looking at the
> problem and most likely this is hardware issue.
95% of these problems are a bad NIC or a bad cable. Since cables are
easy to change I'd try those first, then NICs. Since lots of servers
have dual nics that's a pretty easy change too.
Every now and then it's a bad switch / router.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikolas Everett | 2010-01-07 04:00:42 | Re: noob inheritance question |
| Previous Message | Dmitri Girski | 2010-01-07 02:44:08 | Re: pg_connect takes 3.0 seconds |