Displaying 3 results from an estimated 3 matches for "severethroughput".
2004 Jun 22
1
The truncate_inode_page call in ocfs_file_release causes the severethroughput drop of file reading in OCFS2.
Hi,
We have investigated the possible causes of the severe
throughput drop of file reading in OCFS2 that found in the iozone
benchmark. We find the major cause is the inadequate inode page cache
cleaning when open or close the last reference to an inode.
In routine ocfs_file_release(), if the caller is the last
reference to this inode, truncate_inode_page is called to invalidate all
page
2004 Jun 22
1
The truncate_inode_page call inocfs_file_releasecaus es the severethroughput drop of file reading in OCFS2.
=20
>-----Original Message-----
>From: ocfs2-devel-bounces@oss.oracle.com=20
>[mailto:ocfs2-devel-bounces@oss.oracle.com] On Behalf Of Wim Coekaerts
>Sent: 2004=C4=EA6=D4=C222=C8=D5 16:01
>To: Zhang, Sonic
>
>the problem is, how can we notify. I think we don't want to=20
>notify every
>node on every change othewise we overload the interconnect and we don't
2004 Jul 02
0
[Patch] We resolve the throughput drop problemwhe nr eading filesin OCFS2 volume in the patch "ocfs2-truncate-pages-1.patch"a gainstsvn 1226.
...one closely :)
>> >thanks !
>> >
>> >On Thu, Jul 01, 2004 at 10:39:07AM +0800, Zhang, Sonic wrote:
>> >> Hi,
>> >>=20
>> >> We root caused the problem "The truncate_inode_page call in
>> >> ocfs_file_releasecauses the severethroughput drop of file=20
>reading in
>> >> OCFS2", which we put forward in our former mails. And now, we also
>> >> generate a patch to resolve this problem after one week debugging.
>> >>=20
>> >> This patch is against OCFS2 svn 1226.
>> >&g...