221–230 of 231 posts
Earlier quoted context omitted.
I'm not sure why I'm replying to what look like sockpuppets, but that photo looks nothing like Supermicro equipment. (Of course, "100% designed by our R&D teams" can mean "we sent the ODM a Powerpoint with some diagrams in it".)
I can tell you we did design them because I worked on the hardware as part of the R&D team. We designed the PCBs & software, as we did for the C1.
Dammit. Cheap - very cheap - for everything but storage. It seems impossible to find a low-cost server with some big, slow spinning disks on it at the moment. I'm really not sure why. Anyone got any recommendations there? Where would I look, if anywhere, for, say, 4Tb of storage attached to a low-cost virtual or dedicated server, for less than Google Nearline or equivalent?
Hetzner will give you a server with 24TB for €82/month, or 5TB FTP space at €26/month
Dammit. Cheap - very cheap - for everything but storage. It seems impossible to find a low-cost server with some big, slow spinning disks on it at the moment. I'm really not sure why. Anyone got any recommendations there? Where would I look, if anywhere, for, say, 4Tb of storage attached to a low-cost virtual or dedicated server, for less than Google Nearline or equivalent?
We just introduced an SSD cached storage solution at MNX.io $15/TB -- scalable to 40T. https://mnx.io/pricing
Avotons are very slow, an 8C SoC will typically be slower than an 8 year old 2C desktop CPU (I ran Go builds as a benchmark on my own 2.4 GHz C2750 vs. a 2008 iMac with 2.8 GHz Core 2 Duo). As for Scaleway, some people seem to like it very much, but I found their policy about spamming their users problematic. They (online.net) mock you at registration with a sleazy checked and disabled box for receiving spam ("produc…
I'm happy to run any benchmarks people like (within reason). I can also compare to most AWS instances if you like.
==============================LINUX DATA BELOW===============================
CPU : GenuineIntel Intel(R) Xeon(R) CPU E5-2650L 0 @ 1.80GHz 1800MHz
L2 Cache : 20480 KB
OS : Linux 3.18.26-guest-4-4751b4a-x86_64
C compiler : gcc version 4.9.2 (Debian 4.9.2-10)
libc : libc-2.19.so
MEMORY INDEX : 28.985
INTEGER INDEX : 25.890
FLOATING-POINT INDEX: 39.868
Baseline (LINUX) : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38Earlier quoted context omitted.
Well, that is the whole point, you are suppose to have a whole bunch of small, inexpensive, power efficient, cores. If the software you normally use doesn't take advantage of, at least, multi core hardware, then you can obtain more value from other hosting provider... On the other hand if your software can takes advantages of multicore hardware, or -- even better -- multi node architecture, then scaleway is likely th…
Nearly no web framework is per request multi core (e.g. multi core HTML / JSON rendering, assuming backend operations already async). So each request will be slow. [Edit:] Not sure for the downvote, would be interested what's wrong in my comment.
Though if CPU is the bottleneck in your networked application, you've probably already looked into that.
insanely cheap? For this price you can get a real i7 from Hetzner instead of Atom...
Do you mean through their server bidding? Because those old pieces of junk are known for being stacked with near-failing hard drives.
Earlier quoted context omitted.
Nearly no web framework is per request multi core (e.g. multi core HTML / JSON rendering, assuming backend operations already async). So each request will be slow. [Edit:] Not sure for the downvote, would be interested what's wrong in my comment.
Almost all modern frameworks allow a request to be executed on multiple cores, though if all you're doing is HTML/JSON rendering there would very rarely be any performance advantage to doing so (though if there's an async point it will probably happen, i.e. one core will execute the part up until the call to the backend and then a different core may well pick up the continuation when the result comes back). The actua…
"one core will execute the part up until the call to the backend and then a different core may well pick up the continuation when the result comes back"
This surely helps for one request if your backend or all your microservices are all on one machine, and you have several cores. But if you have your microservices on different machines, multi core will not help you speed up one request if it does not break down rendering of a page in chunks and distribute them to cores (and e.g. combine them with something like Facebook BigPipe (2010 tech)).
And yes multiple cores help with SEDA architectures but request and url parsing (which might be a SEDA stage) is too fast to have any real impact.
[1] http://codemonkeyism.com/a-little-guide-on-using-futures-for...
I just run ServerBear tests and results for the VPS (VC1) are here. http://serverbear.com/benchmark/2016/03/13/sd7vRARnHCYhDa5S