<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Good points, all. I actually wasn't
aware that they were planning a potential lower-end (and
lower-cost) offering; considering that, it might be best to hang
back for now and see what they do along those lines.<br>
<br>
We could certainly move to CentOS 6 or 7 any time we want, with or
without migrating to a new VPS offering. Of course, that would
mean backing everything up that we care about, and several days
(at least) of migration time afterwards. On the other hand,
CentOS 5 end-of-life isn't until 2017, so we have some time, at
least as far as ongoing support for CentOS 5 is concerned....<br>
<br>
--Pat.<br>
<br>
On 4/19/2014 8:17 PM, Justin Smith wrote:<br>
</div>
<blockquote
cite="mid:9e9bb17a-afd7-402c-84b3-39c1d5f16f7c@email.android.com"
type="cite">I'd be all in favor of this if they kept the yearly
payment discount, but they're not. The last thing we need to do
right now is increase costs. <br>
<br>
On the other hand, I have to admit that we're probably not doing
ourselves by clinging to a 32-bit version of Centos 5. I'm all in
favor of stability, but not necessarily at the cost of having to
manually compile software to get anything remotely modern.
Besides, Centos 7 will have systemd and Docker support! Happy
days! <br>
<br>
I don't think there would be much of an impact on litecoin mining
as a result of the core count change. I have two cores on my
digital ocean VPS, and one of those going equals the performance
we see from four cores at linode. <br>
<br>
I could go either way on this one. I feel like it'd be good to
upgrade, but I can see why one would want to leave well enough
alone. <br>
<br>
<div class="gmail_quote">On April 19, 2014 5:49:13 PM EDT, Vance
Kochenderfer <a class="moz-txt-link-rfc2396E" href="mailto:vkochend@nyx.net"><vkochend@nyx.net></a> wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<pre class="k9mail">On Sat, Apr 19, 2014 at 04:20:45PM -0400, Pat Barron wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Yet another upgrade ... Price is the same as we're currently paying.
Should we migrate?
<a moz-do-not-send="true" href="https://blog.linode.com/2014/04/17/linode-cloud-ssds-double-ram-much-more">https://blog.linode.com/2014/04/17/linode-cloud-ssds-double-ram-much-more</a>/
</blockquote>
There are a few downsides. First, the new VPSes are 64-bit only,
so we would have to transition from the current 32-bit setup. I
don't think this is a major problem given that all the software
we're using should be available in 64-bit, but there may be
unforseen glitches. If we decide for a new VPS, it would be worth
considering deploying something newer than CentOS 5.
Another issue is the reduction in number of CPUs available.
Currently we h
ave
eight cores available to us, but actual CPU time
depends on contention with other VPSes on the host machine. The
new model at Linode is to dedicate two cores to the $20/mo. VPSes.
This would impact Justin's litecoin mining, which currently is set
to use four cores. This is more of an experiment than a critical
service, but wanted to point this out. I don't think it would
affect web, mail, etc.
Third, the annual payment discount we are currently getting would
disappear with the new VPS.
However, I am very intrigued by one comment to that post. Caker
hints that there will be a lower-spec plan offered at less than
$20/month. Given that such a VPS would probably offer essentially
the same resources we're using now (except less CPU), I think it's
worth holding out to see what they come up with.
Vance Kochenderfer | "Get me out of these ropes and into a
<a class="moz-txt-link-abbreviated" href="mailto:vkochend@nyx.net">vkochend@nyx.net</a>
|
good belt of Scotch" -Nick Danger
<hr>
wplug-internet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wplug-internet@wplug.org">wplug-internet@wplug.org</a>
<a moz-do-not-send="true" href="http://www.wplug.org/mailman/listinfo/wplug-internet">http://www.wplug.org/mailman/listinfo/wplug-internet</a>
</pre>
</blockquote>
</div>
<br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my
brevity.
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wplug-internet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wplug-internet@wplug.org">wplug-internet@wplug.org</a>
<a class="moz-txt-link-freetext" href="http://www.wplug.org/mailman/listinfo/wplug-internet">http://www.wplug.org/mailman/listinfo/wplug-internet</a>
</pre>
</blockquote>
<br>
</body>
</html>