RE: I/O and db_file_multiblock_read_count
- From: "Kevin Closson" <kevinc@xxxxxxxxxxxxx>
- To: "Matthew Zito" <mzito@xxxxxxxxxxx>, <kevinc@xxxxxxxxxxxxx>, "oracle-l" <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 12 Dec 2006 10:56:01 -0800
ahhh... I haven't touched Sol in 5 years...I guess it shows! Thanks,
Matt
________________________________
From: Matthew Zito [mailto:mzito@xxxxxxxxxxx]
Sent: Tuesday, December 12, 2006 9:51 AM
To: kevinc@xxxxxxxxxxxxx; oracle-l
Subject: RE: I/O and db_file_multiblock_read_count
Nono, its just that on Linux, let's say, cat S.dbf > /dev/null
is fast, but an strace will show that its actually doing a stream of
write()s to the device. On solaris, it does something like (horrible
perl-ish pseudocode):
if ( dest == /dev/null) {
exit 0;
} else {
write(contents, dest);
}
Matt
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Kevin Closson
Sent: Tuesday, December 12, 2006 12:45 PM
To: oracle-l
Subject: RE: I/O and db_file_multiblock_read_count
what? can't dump junk in the bit bucket on Sol? I must
not be gettign your point
________________________________
From: Matthew Zito [mailto:mzito@xxxxxxxxxxx]
Sent: Tuesday, December 12, 2006 9:40 AM
To: kevinc@xxxxxxxxxxxxx; oracle-l
Subject: RE: I/O and
db_file_multiblock_read_count
/dev/null is hard, as some OS'es, solaris
notably, do evil tricks with certain utilities (like cat something to
/dev/null - it returns immediately). Not sure about dd
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Kevin Closson
- References:
- RE: I/O and db_file_multiblock_read_count
- From: Matthew Zito
Other related posts:
- » I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » Re: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- » RE: I/O and db_file_multiblock_read_count
- RE: I/O and db_file_multiblock_read_count
- From: Matthew Zito