| From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Jason Coene" <jcoene(at)gotfrag(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
| Cc: | <mendola(at)bigfoot(dot)com>, <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <josh(at)agliodbs(dot)com> |
| Subject: | Re: Caching of Queries |
| Date: | 2004-09-24 00:05:58 |
| Message-ID: | web-6399646@davinci.ethosmedia.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Jason,
> Sorry, I meant 30,000 with 300 connections - not 3,000. The 300
> connections
> / second is realistic, if not underestimated. As is the nature of
> our site
> (realtime information about online gaming), there's a huge fan base
> and as a
> big upset happens, we'll do 50,000 page views in a span of 3-5
> minutes.
First, your posts show no evidences of the CS storm bug.
Second, 300 *new* connections a second is a lot. Each new connection
requires a significant amount of both database and OS overhead. This
is why all the other web developers use a connection pool.
In fact, I wouldn't be surprised if your lockups are on the OS level,
even; I don't recall that you cited what OS you're using, but I can
imagine locking up Linux 2.4 trying to spawn 300 new processes a
second.
--Josh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2004-09-24 00:37:30 | Re: Caching of Queries |
| Previous Message | Kris Jurka | 2004-09-23 23:47:59 | Re: Large # of rows in query extremely slow, not using |