Flutterby™! : Scaleway

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics


2015-10-09 17:15:15.540189+00 by Dan Lyke 2 comments

A few thoughts on Scaleway servers:

This new pricing lets you enjoy Scaleway services at the smartest price on the market, for €2.99 per month you get a 4 true cores server with 2GB of memory, 50GB of SSD and 200Mbit/s unmetered bandwidth.

At current exchange rates, this is less than $3.50/month. The 4 cores are ARM, and of indeterminate speed. I had been running this site on a Linode server, 25MB of SSD, a gig of RAM, and an Intel VM of indeterminate speed.

The code that runs Flutterby hasn't really changed in somewhere around a decade. There's been a tweak or two, but the core ran back then, and continues to run. It relies on PostgreSQL. Sooo...

time ~/websites/flutterby.com/public_html/archives/viewentry.cgi id=150 > /dev/null0.2321.374
time ~/websites/flutterby.com/public_html/archives/viewentries.cgi fromdate=2015-09-01 todate=2015-10-01 > /dev/null1.815.4
time psql flutterbycms <<< 'select * from articles join users on users.id=articles.author_id join weblogentries on weblogentries.article_id=articles.id where weblogentries.id >= 100 and weblogentries.id <= 5000' > /dev/null~19.5
time perl -le ' = 0; for (0..9999) { for (0..9999) { ++ } };'4.551.8

Note that the web site load seems to be very much helped by mod_perl, because the site doesn't feel that slow (and "shift+reload and counting Mississippi concurs), although the compute and I/O heavier test of loading a month's worth of archives gets slower in the web page.

Also, on that load the month test, there was quite a bit of time not accounted for by user or sys, so there was likely a bunch of I/O, and Scaleway's "SSD" is probably just "SD".

The extra RAM is nice. I got indeterminate GCC errors when trying to compile http://www.trustiosity.com/snow/ on the Linode box that seemed to be related to out of memory, and sure enough, it got past that stage on the Scaleway (there are other problems there...).

Scaleway does their networking with an IPv4 private network, exposing the devices you want public via some sort of NAT, and they don't have IPv6 yet. The ARM core means a few things are weird, you have to recompile any C or C++ you're going to run on them, and you have to jump through a few hoops to get UFW working right...

I'm still trying to decide how valuable my private web presence is these days. I also know that in an hour or three I could cache a bunch of Flutterby to make it serve faster.

And I'm thinking about what a < $3.50/month "cloud" machine means for the mythical Facebook killer.

[ related topics: broadband Perl Open Source Invention and Design History Work, productivity and environment Sports Databases Economics Archival Furniture hubris ]

Inbound links

comments in ascending chronological order (reverse):

#Comment Re: Scaleway made: 2015-10-09 21:04:18.61708+00 by: Dan Lyke

Digging a little deeper...

Looks like CPU is *super* slow... Startup of the boilerplate Perl modules in my CGI scripts, about a second. Time to cat the contents of those same modules to /dev/null, < .016s.

Populating caches now for monthy-by-month archives...

#Comment Re: Scaleway made: 2015-10-11 10:37:32.64051+00 by: meuon [edit]

As I use my Linode server for hosting DNS and other background things for some commercial interests, it's well worth the money I pay them. Their uptime, reliability and support has been very good.

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)

Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.