Andrew Cooke | Contents | Latest | RSS | Twitter | 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

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

C-ORM: docs, API.

Last 100 entries

[Bike] Lessons From 2 Leading 2 Trailing; [Link] Veg Restaurants in Santiago; [Link] List of Contemporary Latin American Authors; [Bike] FTHR; [Link] Whoa - NSA Reduces Collection (of US Residents); [Link] Red Bull's Breitbart; [Link] Linux Threads; [Link] Punycode; [Link] Bull / Girl Statues on Wall Street; [Link] Beautiful Chair Video; Update: Lower Pressures; [Link] Neat Python Exceptions; [Link] Fix for Windows 10 to Avoid Ads; [Link] Attacks on ZRTP; [Link] UK Jazz Invasion; [Review] Cuba; [Link] Aricle on Gender Reversal of US Presidential Debate; {OpenSuse] Fix for Network Offline in Updater Applet; [Link] Parkinson's Related to Gut Flora; Farellones Bike Park; [Meta] Tags; Update: Second Ride; Schwalbe Thunder Burt 2.1 v Continental X-King 2.4; Mountain Biking in Santiago; Books on Ethics; Security Fail from Command Driven Interface; Everything Old is New Again; Interesting Take on Trump's Lies; Chutney v6; References on Entropy; Amusing "Alexa.." broadcast; The Shame of Chile's Education System; Playing mp4 gifs in Firefox on Opensuses Leap 42.2; Concurrency at Microsoft; Globalisation: Uk -> Chile; OpenSuse 42.2 and Synaptics Touch-Pads; Even; Cherry Jam; Lebanese Writer Amin Maalouf; C++ - it's the language of the future; Learning From Trump; Chinese Writer Hu Fayun; And; Apricot Jam; Also; Excellent Article on USA Politics; Oh Metafilter; Prejudice Against The Rurals; Also, Zizek; Trump; Why Trump Won; Doxygen + Latex on CentOS 6; SMASH - Solve 5 Biggest Problems in Physics; Good article on racism, brexit, and social divides; Grandaddy are back!; Consciousness From Max Entropy; Democrats; Harvard Will Fix Black Poverty; Modelling Bicycle Wheels; Amusing Polling Outlier; If Labour keeps telling working class people...; Populism and Choice; Books on Defeat; Enrique Ferrari - Argentine Author; Transcript of German Scientists on Learning of Hiroshima; Calvert Journal; Owen Jones on Twitter; Possible Japanese Authors; Complex American Literature; Chutney v5; Weird Componentized Virus; Interesting Argentinian Author - Antonio Di Benedetto; Useful Thread on MetaPhysics; RAND on fighting online anarchy (2001); NSA Hacked; Very Good LRB Article on Brexit; Nussbaum on Anger; Tasting; Apple + Kiwi Jam; Hit Me; Sudoku - CSP + Chaos; Recycling Electronics In Santiago; Vector Displays in OpenGL; And Anti-Aliased; OpenGL - Render via Intermediate Texture; And Garmin Connect; Using Garmin Forerunner 230 With Linux; (Beating Dead Horse) StackOverflow; Current State of Justice in China; Axiom of Determinacy; Ewww; Fee Chaos Book; Course on Differential Geometry; Okay, but...; Sparse Matrices, Deep Learning; Sounds Bad; Applebaum Rape; Tomato Chutney v4; Have to add...; Culturally Liberal and Nothing More; Weird Finite / Infinite Result

© 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