re Center
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
--
Inaam Rana
EnterpriseDB http://www.enterprisedb.com
g on this patch (dbt2 runs) and it looks like we are
getting the desired results, particularly so when we spread out both sync
and write phases.
--
Inaam Rana
EnterpriseDB http://www.enterprisedb.com
No, I've not tried yet. Inaam-san told me that Linux had a few I/O
schedulers but I'm not familiar with them. I'll find information
about them (how to change the scheduler settings) and try the same
test.
I am sorry, your response just slipped by me. The docs for RHEL (I believe
you are runn
On 12/22/06, Takayuki Tsunakawa <[EMAIL PROTECTED]> wrote:
From: Inaam Rana
> Which IO Shceduler (elevator) you are using?
Elevator? Sorry, I'm not familiar with the kernel implementation, so I
don't what it is. My Linux distribution is Red Hat Enterprise Linux 4.0for
A
9 84
Sorry, I forgot to include the result when using Itagaki-san's patch.
The patch showd the following tps for case (5).
323 350 340 59 225
The best response time was 4 msec, and the worst one was 16 seconds.
Which IO Shceduler (elevator) you are using?
--
Inaam Rana
EnterpriseDB http://www.enterprisedb.com
be a function of total buffers and currently dirty
buffers. Relying on both these values instead of just one static NBuffers
should allow bgwriter to adapt more quickly to workload changes and ensure
that not much work is accumulated for checkpoint.
--
Inaam Rana
EnterpriseDB http://www.enterprisedb.com
I wonder how the other big DBMS, IBM DB2, handles this. Is Itagaki-san
referring to DB2?
DB2 would also open data files with O_SYNC option and page_cleaners
(counterparts of bgwriter) would exploit AIO if available on the system.
Inaam Rana
EnterpriseDB http://www.enterprisedb.com
