ubert Zhang wrote:
> For read, the bottleneck is usually the disk.
> Use iostat to check the utility of your disks.
>
>
>
>
> On Tue, Jul 13, 2010 at 2:07 PM, Peter Schuller <
> peter.schul...@infidyne.com> wrote:
>
>> > Has anyone experimented with differ
For read, the bottleneck is usually the disk.
Use iostat to check the utility of your disks.
On Tue, Jul 13, 2010 at 2:07 PM, Peter Schuller wrote:
> > Has anyone experimented with different settings for concurrent reads? I
> > have set our servers to 4 ( 2 per processor cor
> Has anyone experimented with different settings for concurrent reads? I
> have set our servers to 4 ( 2 per processor core ). I have noticed that
> occasionally, our pending reads will get backed up and our servers don't
> appear to be under too much load. In fact, most of th
if you're not sure where your bottleneck is, you aren't hitting it
hard enough :)
On Mon, Jul 12, 2010 at 9:00 PM, Lee Parker wrote:
> Has anyone experimented with different settings for concurrent reads? I
> have set our servers to 4 ( 2 per processor core ). I h
Has anyone experimented with different settings for concurrent reads? I
have set our servers to 4 ( 2 per processor core ). I have noticed that
occasionally, our pending reads will get backed up and our servers don't
appear to be under too much load. In fact, most of the load appears to be
