Jessica Joy Kerr Profile picture
Apr 4 15 tweets 4 min read
Opening keynote at #qconlondon today: Sophie Wilson, microprocessor designer en.wikipedia.org/wiki/Sophie_Wi…
Moore’s Law was a self-fulfilling prophecy because microprocessor manufacturers set it as their goal to keep up with it.
- Sophie Wilson, #qconlondon
4000 transistors is critical mass for a microprocessor. Fewer than that, you can’t do enough.
the ARM1 had 25000 transistors, in 1985. - Sophie Wilson, designer of the ARM1 #qconlondon
ARM1 was designed using a computer. Its predecessor (the 6502) was laid out by hand. #qconlondon

Reduced instruction set -> smaller number of transistors in the instructor decoder.

32 bit (instead of 8)

Better architecture made it faster
The Firepath microprocessor (2003) does signal processing for DSL everywhere, those green cabinets in the road.
6 million transistors
entirely laid out by a computer
Much more complicated instruction set.
For more power, add more microprocessors…
… limited by Amdahl’s Law.
Adding more processors only helps the parallelizable parts.
Quickly, the sequential part of your program dominates.

If it’s half parallelizable, you can’t exceed a 2x speedup ever.
No automatic compilation of scalar programming languages is going to work,
to scale computation ability with the increasing number of microprocessors in a computer.

We need a revolution in software.
- Sophie Wilson, #qconlondon
“Don’t write anything too slow, because you cannot assume that in the near future, a more powerful computer will come out and make that work.” Sophie Wilson, #QConLondon
For years, microprocessors increased in speed by 50%/year
but now it’s more like 3%.

All we can do is add more processors, so Amdahl’s Law rules.

Sophie Wilson #QConLondon
Now we’re limited not by transistor size, but by power. They’re too hot.
Modern intel processors have high burst performance, but most of the time, they have to keep half the transistors dark.

#QConLondon
Smaller transistors used to mean cheaper, but now the smallest ones are more expensive. (smaller than 28nm)
And don’t use less power.

The “smaller” ones are often smaller in 2D, by sticking up.
Progress has gotten way more expensive. (The easy advances are done.)
Way more researchers (18x more)
way fewer companies (22->3)
Lithography machines (printers for transistors) are way bigger and fancier, now as big as the stage (it’s a big stage) with a laser under the floor

Vacuum chambers where the laser vaporizes drops of tin…

only one company makes them. Hundreds of millions $
Increases will still work for specialized purposes.
But consumers need to adjust expectations:

“The massive gains in scalar performance are over
and costs have stopped dropping, and are now rising!”

Sophie Wilson #QConLondon

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Jessica Joy Kerr

Jessica Joy Kerr Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @jessitron

Apr 5
This morning at #QConLondon , @glenathan tells a story of an experiment at Circle CI: for this greenfield project, let’s have NO LOGGING. ImageImageImage
Instead of logs, events! that make traces!

“Events are good logs.”
They’re data-first instead of human-first; they wrap units of work with durations; they can be explored multiple ways

@glenathan #QConLondon ImageImage
They found best practices like: wrap each unit of work; report errors in a standard field; use span names that are specific enough to tell you what’s happening but general enough for useful grouping.

~ @glenathan #QConLondon ImageImageImage
Read 9 tweets
Apr 5
and now what we’ve all been waiting for: @KevlinHenney keynote #QConLondon

“If there’s any probability, even so close to zero it won’t fit in a floating point number, it is not impossible” Image
Representations are never perfect.
“Software development is the creation and maintaining of illusions.”
@KevlinHenney #QConLondon ImageImage
Programming paradigms are ways to organize our illusions.
@KevlinHenney #QConLondon Image
Read 11 tweets
Apr 4
A deep Java performance talk that I don’t have enough context for, by @PeterLawrey ImageImageImageImage
Project Panama is about replacing JNI. Meantime, if you want to share memory between processes cleverly and safely, you can use their chronicle-bytes library. #QConLondon ImageImageImage
“If you go down to the low level for too long, you wind up writing systems that can’t be altered.” @PeterLawrey #QConLondon Image
Read 5 tweets
Mar 15
This afternoon at #srecon, Adam Mckaig and Tahia Khan from @datadoghq about the evolution of their metrics backend
The high-level architecture looks very familiar to me. The slightly more detailed less so — many parts!
For scale, break up incoming data, put into kafka.
hash(customer_id) -> partition_id
… but then one kafka topic gets overloaded, so…
hash(customer_id) -> topic_id, partition_id
to send to topics in different clusters.
Read 6 tweets
Mar 15
Today at #srecon, @allspaw and @ri_cook give deep insight on real tools, incident timelines, and clumsy automation.
But not in person. 😭
Great tools (as opposed to machines) are near to hand and conform to the person who wields them. Like a hammer, or `top`. Yeah.
They are opinionated, but not prescriptive.

(machines do what they do, and you conform to them)
In software, tools like `top` help us see what’s going on in the digital space.
@ri_cook et al see our work taking place on two sides of a divide. There’s meatspace (where we are) and digital space (where the software runs). You can’t reach out and feel digital stuffs.
Read 13 tweets
Mar 14
What can we learn from ALL the incidents?
@courtneynash at @verica_io compiles reports from lots of companies into the VOID: Verica Open Incident Database. #SREcon
“Software runs the world, and you run that software.”
#SREcon @courtneynash
While every incident and every company is different, the distributions have the same shape. They are “positively skewed:” more short incidents than long ones.
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(