Performance   226442

« earlier    

Comparative Benchmark of Ampere eMAG, AMD EPYC, and Intel XEON for Cloud-Native Workloads | Kinvolk
The Arm CPU architecture has a rich history – starting with home computers in the 1980s (as Acorn RISC Machines), then establishing itself in the 1990s as the dominant architecture for embedded devices, a role that continues today and into the foreseeable future thanks to smartphones. Cloud infrastructure based on the Arm CPU architecture, often seen as exotic only a decade ago, has become more and more generally available in recent years.

As Arm server/instances offerings are becoming more and more ubiquitous in the public cloud, we at Kinvolk were keen to understand the drawbacks and benefits of those offerings for cloud-native applications. We assembled a set of system-level benchmark tests and added automation to execute those benchmarks aimed at gaining insight into the performance of fundamental platform features and functions. We then looked at one implementation in particular – the Ampere eMAG bare-metal servers offered by the Packet IaaS provider – to better understand how this platform compares to more traditional x86 architecture offerings powered by Intel and AMD CPUs. The tools we created are more general though – these benchmarks can easily be run on any Kubernetes cluster; even adding support for new architectures (MIPS, POWER, IA64, etc.) should be straightforward.

It should be noted that Kinvolk has ongoing cooperation with both Ampere Computing and Packet, and used all infrastructure used in our benchmarking free of charge. Ampere Computing furthermore sponsored the development of the control plane automation used to issue benchmark runs, and to collect resulting data points, and to produce charts.

We are releasing the automation for building container images (so the same benchmarks can be run on multiple architectures) as well as scripted automation to perform the below benchmarks to the Open Source community at:
CPU  performance  benchmark  ARM  AMD  Intel 
3 hours ago by euler
Fit on a Floppy
1.44mb Floppy Disk capacity

Websites are getting bigger and bigger. The internet is getting faster and faster but not everywhere at the same pace. A floppy is a physical reminder of filesize.
webdesign  performance  webperf  via:beep 
7 hours ago by dirtystylus
12 Common Mistakes and Missed Optimization Opportunities in SQL | Haki Benita
Most programming languages are designed for professional developers with knowledge of algorithms and data structure. SQL is different. SQL is used by analysts, data scientists, product managers, designers and many others. These professionals have access to databases, but they don't always have the intuition and understanding to write efficient queries. In an effort to make my team write better SQL, I went over reports written by non-developers and code reviews, and gathered common mistakes and missed optimization opportunities in SQL.
database  postgresql  sql  tips  performance  analysis 
11 hours ago by danesparza
🎮 The only Front-End Performance Checklist that runs faster than the others - thedaviddias/
javascript  performance  frontend 
11 hours ago by tedw
Clang-format tanks performance
glibc define some macro to control whether inline toupper, which make include order mattered.

This just seems like clang-format makes program run slow
c++  performance 
21 hours ago by xxr3376

« earlier    

related tags

aio  allocation  amd  analysis  angular  api  application  architecture  arm  asynchronous  audio  aum  aws  battery  benchmark  benchmarks  bestpractices  blog  boards  books  c++  c  cache-coherency  cache  caching  chaos  chrome  cli  cloud  code  common-lisp  common_lisp  comparo  compatibility-telemetry  compression  computer-memory  cors  cost-benefit  cpu  css  culture  daring_fireball  data-oriented  data-structures  database  dbs  debug  development  devops  dictionary  dimensional  disk_drives  diy  django  docker  dsl  dtrace  efficiency  embed  engineering  explanation  facebook  feedback  file-size  fork  frame  freebsd  front-end  frontend  game  generator  go  golang  google  governance  grafana  graphql  ground-up  guide  guidelines  hack  hacks  hardware  hbr  history  host  howto  howtoto  html  http  image  images  important  improvment  influxdb  input-output  intel  intellij  interactive  interesting  interview-prep  io  ios  ipad  java  javascript  job  jokes  js  json  jvm  kernel  kubernetes  layering  learning  legibility  library  linux  lisp  load  mac  macosxhints  mainstage  management  map  marshall  mbp_16  memory  metal-to-virtual  metrics  minimal  minimalism  mixer  mmap  mobile  modular  money-for-time  monitoring  mysql  netflix  network  networking  newsletter  nitty-gritty  opensource  optimisation  optimization  order  orders  organization  osx  packaging  pagination  pandas  people  performance  php  poetry  portland  postgresql  practices  preconnect  productivity  profdev  profiling  programming  pyspark  python  rails  raspberrypi  rate  rca  rds  react-hooks  react  redis  reference  resource  resources  reviews  scene  search  server  share  shell  simplicity  slides  software  spark  speed  spotlight  sprites  sql  startup  state  storage  svg  synth  sysadmin  systems  tcpip  techtariat  test  testing  tidying  tips  tool  toolkit  tools  tradeoffs  trees  tuning  tutorial  types  unit  utility  vegeta  visualization  vr  vsan  vst  w3  web-development  web  webassembly  webdesign  webdev  webpagetest  webperf  webperformance  weekly.rc  windows  work  working-stiff  writing  youtube  zfs  zones 

Copy this bookmark: