Andrew Cooke | Contents | Latest | RSS | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Choochoo Training Diary

Last 100 entries

[Computing] Okular and Postscript in OpenSuse; There's a fix!; [Computing] Fail2Ban on OpenSuse Leap 15.3 (NFTables); [Cycling, Computing] Power Calculation and Brakes; [Hardware, Computing] Amazing Pockit Computer; Bullying; How I Am - 3 Years Post Accident, 8+ Years With MS; Collaboration request; [USA Politics] In America's Uncivil War Republicans Are The Aggressors; [Programming] Selenium and Python; Better Walking Data; [Bike] How Fast Before Walking More Efficient Than Cycling?; [COVID] Coronavirus And Cycling; [Programming] Docker on OpenSuse; Cadence v Speed; [Bike] Gearing For Real Cyclists; [Programming] React plotting - visx; [Programming] React Leaflet; AliExpress Independent Sellers; Applebaum - Twilight of Democracy; [Politics] Back + US Elections; [Programming,Exercise] Simple Timer Script; [News] 2019: The year revolt went global; [Politics] The world's most-surveilled cities; [Bike] Hope Freehub; [Restaurant] Mama Chau's (Chinese, Providencia); [Politics] Brexit Podcast; [Diary] Pneumonia; [Politics] Britain's Reichstag Fire moment; install cairo; [Programming] GCC Sanitizer Flags; [GPU, Programming] Per-Thread Program Counters; My Bike Accident - Looking Back One Year; [Python] Geographic heights are incredibly easy!; [Cooking] Cookie Recipe; Efficient, Simple, Directed Maximisation of Noisy Function; And for argparse; Bash Completion in Python; [Computing] Configuring Github Jekyll Locally; [Maths, Link] The Napkin Project; You can Masquerade in Firewalld; [Bike] Servicing Budget (Spring) Forks; [Crypto] CIA Internet Comms Failure; [Python] Cute Rate Limiting API; [Causality] Judea Pearl Lecture; [Security, Computing] Chinese Hardware Hack Of Supermicro Boards; SQLAlchemy Joined Table Inheritance and Delete Cascade; [Translation] The Club; [Computing] Super Potato Bruh; [Computing] Extending Jupyter; Further HRM Details; [Computing, Bike] Activities in ch2; [Books, Link] Modern Japanese Lit; What ended up there; [Link, Book] Logic Book; Update - Garmin Express / Connect; Garmin Forerunner 35 v 230; [Link, Politics, Internet] Government Trolls; [Link, Politics] Why identity politics benefits the right more than the left; SSH Forwarding; A Specification For Repeating Events; A Fight for the Soul of Science; [Science, Book, Link] Lost In Math; OpenSuse Leap 15 Network Fixes; Update; [Book] Galileo's Middle Finger; [Bike] Chinese Carbon Rims; [Bike] Servicing Shimano XT Front Hub HB-M8010; [Bike] Aliexpress Cycling Tops; [Computing] Change to ssh handling of multiple identities?; [Bike] Endura Hummvee Lite II; [Computing] Marble Based Logic; [Link, Politics] Sanity Check For Nuclear Launch; [Link, Science] Entropy and Life; [Link, Bike] Cheap Cycling Jerseys; [Link, Music] Music To Steal 2017; [Link, Future] Simulated Brain Drives Robot; [Link, Computing] Learned Index Structures; Solo Air Equalization; Update: Higher Pressures; Psychology; [Bike] Exercise And Fuel; Continental Race King 2.2; Removing Lowers; Mnesiacs; [Maths, Link] Dividing By Zero; [Book, Review] Ray Monk - Ludwig Wittgenstein: The Duty Of Genius; [Link, Bike, Computing] Evolving Lacing Patterns; [Jam] Strawberry and Orange Jam; [Chile, Privacy] Biometric Check During Mail Delivery; [Link, Chile, Spanish] Article on the Chilean Drought; [Bike] Extended Gear Ratios, Shimano XT M8000 (24/36 Chainring); [Link, Politics, USA] The Future Of American Democracy; Mass Hysteria; [Review, Books, Links] Kazuo Ishiguro - Never Let Me Go; [Link, Books] David Mitchell's Favourite Japanese Fiction; [Link, Bike] Rear Suspension Geometry; [Link, Cycling, Art] Strava Artwork; [Link, Computing] Useful gcc flags; [Link] Voynich Manuscript Decoded; [Bike] Notes on Servicing Suspension Forks

© 2006-2017 Andrew Cooke (site) / post authors (content).

Thinking About Databases, Efficiency and Technology

From: "andrew cooke" <andrew@...>

Date: Sat, 22 Nov 2008 17:20:53 -0300 (CLST)

The discussion at
http://ask.metafilter.com/82769/How-is-Facebook-doing-its-queries made me
think a little.

Some of the comments there seemed a bit confused about the concepts
involved.  The biggest confusion seemed to be between implementation and
logical function.

While my experience is limited to smaller projects, I have found that
managing data efficiently generally depends very much on the particular
circumstances at the time.  The best solution will involve trade-offs that
exploit particular details of the problem at hand.

That doesn't mean that there are not certain useful technologies.  You are
almost always going to use a database, for example.  But those
technologies are going to be complex, and to use the efficiently you will
need to first understand what you are going to do in logical terms, and
then how to do that within a particular tool.

So in the discussion I was reading the "right" answer is not going to be
"use technology X".  It is going to be "do X; it can be achieved with
technology Y in this way or with technology Z in this way".


It is worth thinking about whether there is a problem at all.  One
particularly odd answer in that discussion was raving about hibernate.  I
wonder if the poster had ever considered how a database is implemented,
looked at the obvious correspondence between foreign keys and Java
references, or understood that a database can also cache data in memory.

It seems fairly clear that there is only a problem, then, if there is too
much data to fit into memory.  And even then, it is not clear that
explicit caching is going to improve performance - a database also capable
of caching recent results internally.

Yet it's also obvious explicit caching (eg memcache) works - everyone uses
it.  Why?

There seem to be two answers to that.  First, it's simpler (and more
familiar to many programmers) than configuring a complex database
solution.  I imagine that in many cases you could have careful data
partitioning and denormalisation (incidentally, as far as I can tell, this
is "sharding" - see
http://highscalability.com/unorthodox-approach-database-design-coming-shard),
or master/slave databases doing the same job (although this is going to
depend on the database - there is probably a financial factor here).

Second, explicit caching lets you trade consistency for efficiency.  To
some extent you can get this with databases by ignoring transactions, but
I suspect an explicit cache lets you take the idea much further.

Is that it?

I need to read more at http://highscalability.com/

Andrew

Comment on this post