From: Nick Owens <mischief@offblast.org>
To: 9front@9front.org
Subject: Re: [9front] vmx(1) OpenBSD: SSD vs sparse file
Date: Wed, 14 Nov 2018 20:54:15 -0800 [thread overview]
Message-ID: <CAH_zEu6mxYzocLQQMQVfgM0kDVKsXMz=ML6et+HbiWwQ-TufiA@mail.gmail.com> (raw)
In-Reply-To: <74A45A65B7605C93BEDDCF56425F1877@ewsd.inri.net>
could be due to the in-memory block cache that hjfs has? if a program
(like vmx) talks to devsd directly (/dev/sdE0/openbsd or whatever)
there's no cache.
On Wed, Nov 14, 2018 at 7:20 PM <sl@stanleylieber.com> wrote:
>
> Subjective observation:
>
> On my CORE i7 ThinkPad X250, vmx(1) seems to run OpenBSD/amd64 6.3
> appreciably faster when OpenBSD is installed in a sparse file stored
> on the 9front hjfs file system (which is itself running on an SSD)
> than when OpenBSD is installed on its own SSD and vmx(1) is accessing
> its hard drive directly via the -d flag.
>
> sl
next parent reply other threads:[~2018-11-15 4:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <74A45A65B7605C93BEDDCF56425F1877@ewsd.inri.net>
2018-11-15 4:54 ` Nick Owens [this message]
2018-11-15 6:34 ` Matthew Veety
2018-11-15 6:36 ` Stanley Lieber
2018-11-15 14:30 ` hiro
2018-11-15 14:38 ` Stanley Lieber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH_zEu6mxYzocLQQMQVfgM0kDVKsXMz=ML6et+HbiWwQ-TufiA@mail.gmail.com' \
--to=mischief@offblast.org \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).