From: | Scott Carey <scott(at)richrelevance(dot)com> |
---|---|
To: | Andrej <andrej(dot)groups(at)gmail(dot)com> |
Cc: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>, Jeff <threshar(at)torgo(dot)978(dot)org>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: random_page_cost vs ssd? |
Date: | 2009-03-11 19:28:56 |
Message-ID: | C5DD5F07.32E1%scott@richrelevance.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Google > “linux drop_caches” first result:
http://www.linuxinsight.com/proc_sys_vm_drop_caches.html
To be sure a test is going to disk and not file system cache for everything in linux, run:
‘sync; cat 3 > /proc/sys/vm/drop_caches’
On 3/11/09 11:04 AM, "Andrej" <andrej(dot)groups(at)gmail(dot)com> wrote:
2009/3/12 Scott Carey <scott(at)richrelevance(dot)com>:
> [...snip...]. All tests start with 'cat 3 > /proc/sys/vm/drop_caches', and work on
> a 32GB data set (40% of the disk).
What's the content of '3' above?
--
Please don't top post, and don't use HTML e-Mail :} Make your quotes concise.
From | Date | Subject | |
---|---|---|---|
Next Message | hubert depesz lubaczewski | 2009-03-11 19:32:27 | Re: random_page_cost vs ssd? |
Previous Message | Frank Joerdens | 2009-03-11 19:27:10 | Full statement logging problematic on larger machines? |