From: Yuri Weinstein <yweinste@redhat.com>
To: Sage Weil <sage@newdream.net>
Cc: sepia@ceph.com, ceph-devel@vger.kernel.org,
Loic Dachary <ldachary@redhat.com>,
Xinxin Shu <xinxin.shu@intel.com>,
Alfredo Deza <adeza@redhat.com>
Subject: Re: VPS memory
Date: Thu, 18 Jun 2015 00:49:18 -0400 (EDT) [thread overview]
Message-ID: <913834281.25220323.1434602958096.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1506172011510.23826@cobra.newdream.net>
I am all for it!
Thx
YuriW
----- Original Message -----
From: "Sage Weil" <sage@newdream.net>
To: "Yuri Weinstein" <yweinste@redhat.com>
Cc: sepia@ceph.com, ceph-devel@vger.kernel.org, "Loic Dachary" <ldachary@redhat.com>, "Xinxin Shu" <xinxin.shu@intel.com>, "Alfredo Deza" <adeza@redhat.com>
Sent: Wednesday, June 17, 2015 8:13:17 PM
Subject: VPS memory
On Wed, 17 Jun 2015, Yuri Weinstein wrote:
> - upgrade/dumpling-firefly-x (to hammer)(distros) - runs out of memory on vps and unreliable
How about we
- half the number of vps's per node.
- double the default ram per vps instance
- double the cpu?
It'll mean lower test throughput, but (hopefully) reliable test results.
Given the amount of time we waste sifting through noisy results that seems
like a better path?
sage
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-18 4:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <515457523.22063779.1434385426136.JavaMail.zimbra@redhat.com>
2015-06-15 16:37 ` firefly v0.80.10 QE validation status 6/15/2015 Yuri Weinstein
2015-06-15 17:19 ` Samuel Just
2015-06-16 10:02 ` Gregory Farnum
2015-06-18 1:33 ` firefly v0.80.10 QE validation completed Yuri Weinstein
2015-06-18 3:13 ` VPS memory Sage Weil
2015-06-18 4:49 ` Yuri Weinstein [this message]
2015-06-18 20:43 ` Tamil Muthamizhan
2015-06-22 7:40 ` firefly v0.80.10 QE validation completed Olivier Bonvalet
2015-06-22 8:48 ` Loic Dachary
2015-06-22 8:52 ` Dan van der Ster
2015-06-22 9:12 ` Loic Dachary
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=913834281.25220323.1434602958096.JavaMail.zimbra@redhat.com \
--to=yweinste@redhat.com \
--cc=adeza@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ldachary@redhat.com \
--cc=sage@newdream.net \
--cc=sepia@ceph.com \
--cc=xinxin.shu@intel.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.