[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
need a server-busting test case
From: |
Ted Stern |
Subject: |
need a server-busting test case |
Date: |
Tue, 15 Apr 2008 15:47:31 -0700 |
User-agent: |
Gnus/5.110007 (No Gnus v0.7) Emacs/23.0.60 (gnu/linux) |
Hi all,
At a company That Shall Not Be Named, the bean counters in IT support
are telling us that our new server can't be a standalone workstation.
Instead, they're going to give us a virtual Linux server on a
mainframe.
We will be running various SCM utilities on this server. That means
some web hosting, CVS, subversion, bugzilla, etc.
A virtual server in itself wouldn't be so bad, but this one will be
static -- it will have about half the memory and I/O bandwidth and
capacity of the standalone Linux workstation we had envisioned. This
doesn't make a lot of sense to me, since it seems like we're going
backwards from what we have now.
So I'm trying to come up with a test case we can use to break the
server, in order to show that their assessment of our requirements is
incorrect.
Is there something I can do with CVS that will demonstrate high I/O
and/or memory requirements? I have access to a repository with ~43K
files. Would it suffice to have some tagging, checkouts and commits
going (almost) concurrently?
Ted
--
dodecatheon at gmail dot com
Frango ut patefaciam -- I break so that I may reveal
- need a server-busting test case,
Ted Stern <=