From: "Kirk True" <ktrue@movaris.com>
To: linux-mm@kvack.org
Subject: VM benchmarking help?
Date: Thu, 12 Feb 2004 08:25:45 -0800 [thread overview]
Message-ID: <840273B2CF2C534E894D9705984C88F4930885@mail.corp.movaris.com> (raw)
Hi all,
Are there any resources that detail how to effectively benchmark the VM? How do I write test cases that are accurate and representative of certain usages? Under what environment(s) should these tests be run (e.g. is running under UML unhelpful?)? What metrics should be measured: time, number of faults, swapping, allocations, deallocations, etc.? What's the best format to report these findings and tweak them? Might a good first step might be to run other's test cases and provide more data points? If so, where can these tests - and directions on how to execute them - be found?
I'd like to help out but I need some guidance in doing so :)
Thanks!
Kirk
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
reply other threads:[~2004-02-12 16:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=840273B2CF2C534E894D9705984C88F4930885@mail.corp.movaris.com \
--to=ktrue@movaris.com \
--cc=linux-mm@kvack.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