From: Mike Brady <mike.brady@devnull.net.nz>
To: xen-devel@lists.sourceforge.net
Subject: Re: RAM allocation and miscellaneous questions
Date: Sat, 2 Oct 2004 09:20:02 +1200 [thread overview]
Message-ID: <200410020920.02505.mike.brady@devnull.net.nz> (raw)
In-Reply-To: <E1CCwpW-000695-00@mta1.cl.cam.ac.uk>
The parts are readily available in NZ and I would be surprised if you couldn't
find a local supplier in Wellington to put a system together for you. You
would be getting support for the parts rather than support for the system in
this case though. Which is what I assume the issue would be.
On Thursday 30 September 2004 21:02, Keir Fraser wrote:
> How odd -- I expected that in most places there would be multiple
> white-box vendors selling Opteron-based systems. It's not like the
> component parts are in short supply. Except maybe in NZ. :-)
>
> -- Keir
>
> > Hmmmmmm. Lots of RAM :o)
> >
> > Yes, I do have a 'cluster', but only two machines so far. The problem for
> > me is that multi-processor Opteron 1u machines (or 2u or 4u for that
> > matter) are hard to come by here in New Zealand, unless we pay through
> > the nose for an HP or other big-name machine. I can get dual Xeon
> > machines pretty cheap though. If I look at the Opteron option, I'll have
> > to compare it to just buying more Xeons. Either way, it's going to cost
> > more for our initial cluster than it would if I could just use 12GB in a
> > cheap Xeon unit. Don't get me wrong though, if Opteron units were
> > available here I would have got them from the outset.
> >
> > Personally I have no issue with sourcing machines from Australia or
> > somewhere, but my bosses will be reluctant due to support issues, etc.
> >
> > Regards,
> > Paul
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-01 21:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 2:57 RAM allocation and miscellaneous questions Paul Dorman
2004-09-29 3:30 ` Mark A. Williamson
2004-09-29 4:57 ` Paul Dorman
2004-09-29 7:55 ` Ian Pratt
2004-09-29 12:26 ` Mark A. Williamson
2004-09-29 8:37 ` Keir Fraser
2004-09-29 19:16 ` Paul Dorman
2004-09-29 19:53 ` Ronald G. Minnich
2004-09-30 9:02 ` Keir Fraser
2004-10-01 21:20 ` Mike Brady [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-29 11:12 Mat
2004-09-30 8:26 ` Ian Pratt
2004-09-30 13:26 ` Mark A. Williamson
2004-09-30 20:21 ` Brian Wolfe
2004-09-30 20:24 ` Mark A. Williamson
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=200410020920.02505.mike.brady@devnull.net.nz \
--to=mike.brady@devnull.net.nz \
--cc=xen-devel@lists.sourceforge.net \
/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.