| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: amazon ec2 |
| Date: | 2011-05-05 00:02:53 |
| Message-ID: | 4DC1E92D.5020904@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> FWIW, EnterpriseDB's "InfiniCache" provides the same caching benefit. The way that works is when PG goes to evict a page from shared buffers that page gets compressed and stuffed into a memcache cluster. When PG determines that a given page isn't in shared buffers it will then check that memcache cluster before reading the page from disk. This allows you to cache amounts of data that far exceed the amount of memory you could put in a physical server.
So memcached basically replaces the filesystem?
That sounds cool, but I'm wondering if it's actually a performance
speedup. Seems like it would only be a benefit for single-row lookups;
any large reads would be a mess.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | david | 2011-05-05 00:12:30 | Re: amazon ec2 |
| Previous Message | Josh Berkus | 2011-05-04 18:44:22 | Re: Postgres 9.0.4 + Hot Standby + FusionIO Drive + Performance => Query failed ERROR: catalog is missing 1 attribute(s) for relid 172226 |