From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
hui81.qi@samsung.com, kundan.kumar@samsung.com,
kdevops@lists.linux.dev
Subject: Re: [PATCH 0/2] kdevops: add milvus with minio support
Date: Thu, 28 Aug 2025 19:05:40 -0700 [thread overview]
Message-ID: <aLEK9MIzcUd3JF27@bombadil.infradead.org> (raw)
In-Reply-To: <20250827093202.3539990-1-mcgrof@kernel.org>
On Wed, Aug 27, 2025 at 02:31:59AM -0700, Luis Chamberlain wrote:
> This adds the ability to test milvus on minio with different filesystem
> configuration targets. There's a basic configuration you can run which
> will just support one default filesystem, which will be used where you
> place your docker image and also where we place the minio instance. Then
> there is multifs support where just as with fstests support on kdevops
> you can select a slew of different filesystem targets to try to test.
>
> Recommendation is to stick to 40 iterations at 1,000,000 tests unless
> you have more than 100 GiB per guest to spare. If you have space to
> spare then you know how to ballpark it.
>
> On High Capacity SSDs, the world is our oyster.
>
> You can see a demo of results here:
>
> https://github.com/mcgrof/demo-milvus-kdevops-results
>
> These are just demos. On guests. Nothing really useful.
> I should point out this has AB testing automated as well so we can
> leverage this to test for instance ... parallel writeback in an
> automated way ;)
>
> If you want to test this you can also use this branch on kdevops:
>
> https://github.com/linux-kdevops/kdevops/tree/mcgrof/20250827-milvus
>
> I am in hopes someone will just prompt an AI for bare metal support
> while I sleep. It should be... easy. Just create the partitions already,
> use one host and ask the prompt to not mkfs for you. So don't use
> multi-fs support at first. Just use the option to create the storage
> partition where you place docker. In fact you can copy and paste this
> prompt the the AI, and I think it will know what to do. You just skip
> some steps as the filesystems can be created and mounted for you. You
> just need the host file created by you manually for the target node.
> That and infer user and group id support (WORKFLOW_INFER_USER_AND_GROUP).
Pushed.
Luis
prev parent reply other threads:[~2025-08-29 2:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 9:31 [PATCH 0/2] kdevops: add milvus with minio support Luis Chamberlain
2025-08-27 9:32 ` [PATCH 1/2] ai: add Milvus vector database benchmarking support Luis Chamberlain
2025-08-27 9:32 ` [PATCH 2/2] ai: add multi-filesystem testing support for Milvus benchmarks Luis Chamberlain
2025-08-27 14:47 ` Chuck Lever
2025-08-27 19:24 ` Luis Chamberlain
2025-09-01 20:11 ` Daniel Gomez
2025-09-01 20:27 ` Luis Chamberlain
2025-08-29 2:05 ` Luis Chamberlain [this message]
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=aLEK9MIzcUd3JF27@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=cel@kernel.org \
--cc=da.gomez@kruces.com \
--cc=hui81.qi@samsung.com \
--cc=kdevops@lists.linux.dev \
--cc=kundan.kumar@samsung.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.