On Wed, Aug 18, 2010 at 7:37 AM, erik quanstrom <[email protected]> wrote:
>> On Tue, Aug 17, 2010 at 11:55 AM, Brad Frank <[email protected]> wrote:
>> > Yes, doing those things would be an alternative. But the bigger question is
>> > why is fossil hitting the load like that while running in Qemu. And also,
>> > another question is whether this would be happening on physical hardware as
>> > well... Is there anything I can do to figure out why it is doing that, and
>> > how to resolve it?
>
> has anyone tried aoe with qemu? vblade running in the host
> might be faster. devaoe(3)/sdaoe(3) from 9atom allow
> 128 outstanding requests), which should help with latency
> a bit more.
>
I haven't tried it, but I agree that it is likely faster. An even
better solution would be use of the virtio disk or 9p drivers, but I'm
not sure they are available in vanilla qemu. I don't recall seeing
these delays with qemu-kvm on my laptop when I was running off a
virtio disk -- same thing goes for lguest for those not running on a
KVM-able processor.
-eric
