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.
Go's net/http framework uses a go routine per connection.
C2: Affordable X86-64 Servers
181–190 of 231 posts
Re: C2: Affordable X86-64 Servers
#182Earlier quoted context omitted.
If nbench only uses 1 core, yes, my comparison is wrong. Is there a similar benchmarking linux tool that can use many cores? edit: instance is a t2.micro
I don't think the comparison is wrong per se; this actually makes it a bit easier, since you're just comparing one core to another. The only thing that I think is problematic is comparing a t2 to anything else, since that CPU performance is not sustainable as it might be elsewhere. m3 and m4 (and other instance types @ aws) are not explicitly throttled. (Source: AWS Solutions Architect) We're running a portion of our…
Re: C2: Affordable X86-64 Servers
#183Earlier quoted context omitted.
I'm happy to run any benchmarks people like (within reason). I can also compare to most AWS instances if you like.
Please run nbench [1]. I ran it on the C1 in April 2015 and got the following results: CPU : 4 CPU L2 Cache : OS : Linux 3.2.34-29 C compiler : gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1) libc : libc-2.19.so MEMORY INDEX : 5.859 INTEGER INDEX : 8.164 FLOATING-POINT INDEX: 5.770 For comparison, here are an Intel Atom N450, a Core 2 Duo L7500 and a Raspberry Pi 1 Model B: CPU : Dual GenuineIntel Intel(R) Atom(TM)…
CPU : 8 CPU GenuineIntel Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz 3910MHz
L2 Cache : 8192 KB
OS : Linux 3.16.0-55-generic
C compiler : gcc version 4.8.4 (Ubuntu 4.8.4- 2ubuntu1~14.04.1)
libc : libc-2.19.so
MEMORY INDEX : 58.235
INTEGER INDEX : 52.421
FLOATING-POINT INDEX: 79.472
Baseline (LINUX) : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38Re: C2: Affordable X86-64 Servers
#184Earlier quoted context omitted.
Please run nbench [1]. I ran it on the C1 in April 2015 and got the following results: CPU : 4 CPU L2 Cache : OS : Linux 3.2.34-29 C compiler : gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1) libc : libc-2.19.so MEMORY INDEX : 5.859 INTEGER INDEX : 8.164 FLOATING-POINT INDEX: 5.770 For comparison, here are an Intel Atom N450, a Core 2 Duo L7500 and a Raspberry Pi 1 Model B: CPU : Dual GenuineIntel Intel(R) Atom(TM)…
Benchmark from Intel i7 desktop CPU : 8 CPU GenuineIntel Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz 3910MHz L2 Cache : 8192 KB OS : Linux 3.16.0-55-generic C compiler : gcc version 4.8.4 (Ubuntu 4.8.4- 2ubuntu1~14.04.1) libc : libc-2.19.so MEMORY INDEX : 58.235 INTEGER INDEX : 52.421 FLOATING-POINT INDEX: 79.472 Baseline (LINUX) : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38
CPU :
L2 Cache :
OS : Darwin 15.3.0
C compiler : Apple LLVM version 7.0.2 (clang-700.1.81)
libc :
MEMORY INDEX : 49.009
INTEGER INDEX : 41.947
FLOATING-POINT INDEX: 92.671
Baseline (LINUX) : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38Re: C2: Affordable X86-64 Servers
#185Earlier quoted context omitted.
I'm happy to run any benchmarks people like (within reason). I can also compare to most AWS instances if you like.
Please run nbench [1]. I ran it on the C1 in April 2015 and got the following results: CPU : 4 CPU L2 Cache : OS : Linux 3.2.34-29 C compiler : gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1) libc : libc-2.19.so MEMORY INDEX : 5.859 INTEGER INDEX : 8.164 FLOATING-POINT INDEX: 5.770 For comparison, here are an Intel Atom N450, a Core 2 Duo L7500 and a Raspberry Pi 1 Model B: CPU : Dual GenuineIntel Intel(R) Atom(TM)…
CPU : 4 CPU GenuineIntel Intel(R) Core(TM) i5-3570S CPU @ 3.10GHz 3706MHz
L2 Cache : 6144 KB
OS : Linux 3.14.32-xxxx-grs-ipv6-64
C compiler : gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.1)
libc : libc-2.19.so
MEMORY INDEX : 51.103
INTEGER INDEX : 48.049
FLOATING-POINT INDEX: 68.238
Baseline (LINUX) : AMD K6/233*, 512 KB L2-cache, gcc 2.7.2.3, libc-5.4.38
Re: C2: Affordable X86-64 Servers
#186Re: C2: Affordable X86-64 Servers
#187If you do CPU-intensive work on these servers, might not the electricity cost surpass the 0.02/hour income? Example: if a kWh costs 0.10, then to have something burning 200W costs 0.02 per hour. (Someone substitute real-ish numbers.)
Re: C2: Affordable X86-64 Servers
#188Re: C2: Affordable X86-64 Servers
#189Earlier quoted context omitted.
> I doubt that Just tried for a few minutes all 3 of them. The C2S is a C2550, and the C2M and C2L are C2750. They each appear to be bare metal, and not virtualized. The VPS offering, which is advertised as a VPS, appears to be virtualized inside of a C2750. The C1 is a Marvell Armada 370/XP, a bare metal ARMv7l board. > I would consider their offers "ad-supported". This also is not my experience. I haven't ever rece…
> They each appear to be bare metal, and not virtualized How can you tell?
* loaded drivers may be named after the virtualization platform (VMware)
* CPUs can be reported as "Virtual" in /proc/cpuinfo
* Special files in /proc (for instance "vz" for OVZ)
* Kernel name
* etc.
Re: C2: Affordable X86-64 Servers
#190Avotons 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…
Not based on SuperMicro MicroBlades, home R&D design : https://twitter.com/scaleway/status/707617919434412034