RM:
I do not understand - why in some cases with smaller block writing
block twice could be actually faster than doing it once every time?
I definitely am missing something here...
In addition to what Neil said, I want to add that
when an application O_DSYNC write cover only parts of
Robert Milkowski writes:
Hello Neil,
Thursday, August 10, 2006, 7:02:58 PM, you wrote:
NP Robert Milkowski wrote:
Hello Matthew,
Thursday, August 10, 2006, 6:55:41 PM, you wrote:
MA On Thu, Aug 10, 2006 at 06:50:45PM +0200, Robert Milkowski wrote:
btw: wouldn't
Hello Matthew,
Tuesday, August 8, 2006, 8:08:39 PM, you wrote:
MA On Tue, Aug 08, 2006 at 10:42:41AM -0700, Robert Milkowski wrote:
filebench in varmail by default creates 16 threads - I configrm it
with prstat, 16 threrads are created and running.
MA Ah, OK. Looking at these results, it
Robert Milkowski wrote:
Hello Matthew,
Thursday, August 10, 2006, 6:55:41 PM, you wrote:
MA On Thu, Aug 10, 2006 at 06:50:45PM +0200, Robert Milkowski wrote:
btw: wouldn't it be possible to write block only once (for synchronous
IO) and than just point to that block instead of copying it
Robert Milkowski wrote:
Hello Neil,
Thursday, August 10, 2006, 7:02:58 PM, you wrote:
NP Robert Milkowski wrote:
Hello Matthew,
Thursday, August 10, 2006, 6:55:41 PM, you wrote:
MA On Thu, Aug 10, 2006 at 06:50:45PM +0200, Robert Milkowski wrote:
btw: wouldn't it be possible to write
Hello Doug,
Tuesday, August 8, 2006, 7:28:07 PM, you wrote:
DS Looks like somewhere between the CPU and your disks you have a limitation
of 9500 ops/sec.
DS How did you connect 32 disks to your v440?
Some 3510 JBODs connected directly over FC.
--
Best regards,
Robert
filebench in varmail by default creates 16 threads - I configrm it with prstat,
16 threrads are created and running.
bash-3.00# lockstat -kgIW sleep 60|less
Profiling interrupt: 23308 events in 60.059 seconds (388 events/sec)
Count genr cuml rcnt nsec Hottest CPU+PILCaller
On Tue, Aug 08, 2006 at 10:42:41AM -0700, Robert Milkowski wrote:
filebench in varmail by default creates 16 threads - I configrm it
with prstat, 16 threrads are created and running.
Ah, OK. Looking at these results, it doesn't seem to be CPU bound, and
the disks are not fully utilized either.
