qa   9579

« earlier    

Introduction - Pact
Pact is a contract testing tool. Contract testing is a way to ensure that services (such as an API provider and a client) can communicate with each other. Without contract testing, the only way to know that services can communicate is by using expensive and brittle integration tests.
framework  testing  contracts  api  software  tool  system  qa 
5 days ago by aviflax
cpu - How to know number of cores of a system in Linux? - Unix & Linux Stack Exchange
To get a complete picture you need to look at the number of [threads][1] per core, [cores][2] per socket and [sockets][3]. If you multiply these numbers you will get the number of [CPUs][4] on your system.

> CPUs = Threads per core X cores per socket X sockets

CPUs are what you see when you run `htop` (these do not equate to physical CPUs).

Here is an example from a desktop machine:

$ lscpu | grep -E '^Thread|^Core|^Socket|^CPU\('
CPU(s): 8
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1

And a server:

$ lscpu | grep -E '^Thread|^Core|^Socket|^CPU\('
CPU(s): 32
Thread(s) per core: 2
Core(s) per socket: 8
Socket(s): 2

The output of `nproc` corresponds to the CPU count from `lscpu`. For the desktop machine above this should match the 8 CPU(s) reported by `lscpu`:

$ nproc --all
8

The output of `/proc/cpuinfo` should match this information, for example on the desktop system above we can see there are 8 processors (CPUs) and 4 cores (core id 0-3):

$ grep -E 'processor|core id' /proc/cpuinfo
processor : 0
core id : 0
processor : 1
core id : 0
processor : 2
core id : 1
processor : 3
core id : 1
processor : 4
core id : 2
processor : 5
core id : 2
processor : 6
core id : 3
processor : 7
core id : 3

The `cpu cores` reported by `/proc/cpuinfo` corresponds to the `Core(s) per socket` reported by `lscpu`. For the desktop machine above this should match the 4 Core(s) per socket reported by lscpu:

$ grep -m 1 'cpu cores' /proc/cpuinfo
cpu cores : 4

To specifically answer your question you tell how many cores you have by multiplying the number of cores you have per socket by the number of sockets you have.

> Cores = Cores per socket X Sockets

For the example systems above the desktop has 4 cores:

$ echo Cores = $(( $(lscpu | awk '/^Socket/{ print $2 }') * $(lscpu | awk '/^Core/{ print $4 }') ))
Cores = 4

While the server has 16:

$ echo Cores = $(( $(lscpu | awk '/^Socket/{ print $2 }') * $(lscpu | awk '/^Core/{ print $4 }') ))
Cores = 16

Another useful utility is `dmidecode` which outputs per socket information. In the case of the server system listed above we expect to see 8 cores per socket and 16 threads per socket:

$ sudo dmidecode -t 4 | grep -E 'Socket Designation|Count'
Socket Designation: CPU1
Core Count: 8
Thread Count: 16
Socket Designation: CPU2
Core Count: 8
Thread Count: 16

In summary:

- You need to be aware of sockets, cores and threads
- You need to be careful of the term CPU as it means different things in different contexts


[1]: https://en.wikipedia.org/wiki/Simultaneous_multithreading
[2]: https://en.wikipedia.org/wiki/Multi-core_processor
[3]: https://en.wikipedia.org/wiki/CPU_socket
[4]: https://en.wikipedia.org/wiki/Central_processing_unit
siparcs  QA 
15 days ago by quamash
Twitter
RT : As a , it can sometimes feel like you're not valued within your . ThoughtWorker Lina Zubyte shares her 5 ti…
QA  team  from twitter
15 days ago by noahsussman
Unit test your Java architecture - ArchUnit
Start enforcing your architecture within 30 minutes using the test setup you already have.
architecture  junit  Java  testing  architect  opensource  development  framework  qa  2019 
28 days ago by dchesters
Pactflow | Distributed systems testing made easy
Simplify your contract testing with Pactflow

The first contract-testing platform for collaborating on and testing distributed systems
testing  qa 
5 weeks ago by dserodio
Component Testing Plans
Quality stems from and is proven by an implemented testing plan by which components are inspected prior to release. This article describes criteria and tools for testing components and how to order making them at a high level to help teams plan.
testing  components  qa  accessibility  design 
6 weeks ago by spaceninja
TonicAI/masquerade: A Postgres Proxy to Mask Data in Realtime
Masquerade is two things. It is a TCP proxy that sits between your Postgres Database and client and proxies data back and forth. The proxy listens to all messages sent from the database to the client and provides a hook for users to modify data in-transit and before being received by the client. Second, it is a masker. It has built-in functionality that can mask sensitive data in the database so that it cannot be seen by the client.
postgresql  database  security  testing  qa 
6 weeks ago by dserodio
Stack Overflow for Teams
meant for organization internal use, i think
qa  knowlegebase  kb  qanda 
6 weeks ago by reedhedges
MailDev - Create better email during development
docker run -p 1080:80 -p 1025:25 djfarrelly/maildev
mail  docker  testing  mailforspam  qa 
6 weeks ago by josephishak

« earlier    

related tags

2019  accessibility  address  agile  analysis  android  api  app  appium  apple  application  appsscript  architect  architecture  automated_testing  automation  aviation  azure  boeing  browser_testing  bugs  build  business  capsule  cd  chaos  character  check  ci  cloudcomputing  code  community  components  contracts  control  corpus  correctness  csv  customersupport  customersupporttool  cypress  data  database  datasets  deep  design  dev  developer  development  devops  dns  docker  documentation  domain  ecommerce  electronics  email  emascript  engineer  engineering  feminism  forum  fqdn  framework  frontend  fuzz  gas  git  github  google  hardening  health  history  howto  http  humor  ifttt  image  information  input  instagram  interview  ios  ipynb  ixr  java  javascript  jira  js  json  jtbd  junit  jupyter  kb  keyboard  knowlegebase  learning  length  licensing  limit  linter  load  logs  long  machine-learing  machine  macos  mail  mailforspam  management  manufacturing  materials  maximum  meditation  microencapsulation  microfluidics  microservices  microsoft  mobile  name  nbstats  network  nlp  nodejs  notebookprofiling  npm  observability  opensource  ops  oss  ou2.0  our-journey  parser  parsing  pattern  percy  performance  php  phpbb  pop  postgresql  pr  processing  product  production  programming  proxy  pull  qanda  qc  quality  reddit  reference  request  research  retail  review  safety  scala  science  se  security  selenium  server  service  shell  silicone  siparcs  smtp  software-development  software  software_testing  softwaretesting  startup  strategy  studio  supplements  support  supporttool  sweng  system  tdd  team  test  test_runner  testing  tm351  tool  tools  tradesy  travis-ci  tutorial  twitter  uat  unreliable  uri  url  uv  validation  video  visual-testing  visual  voxable-studio  vue  web  webdev  windows  youtube 

Copy this bookmark:



description:


tags: