| 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

Crypto AG DID work with NSA / GCHQ; UNUMS (Universal Number Format); MOOCs (Massive Open Online Courses); Interesting Looking Game; Euler's Theorem for Polynomials; Weeks 3-6; Reddit Comment; Differential Cryptanalysis For Dummies; Japanese Graphic Design; Books To Be Re-Read; And Today I Learned Bugs Need Clear Examples; Factoring a 67 bit prime in your head; Islamic Geometric Art; Useful Julia Backtraces from Tasks; Nothing, however, is lost with less discomfort than that which, when lost, cannot be missed; Article on Didion; Cost of Living by City; British Slavery; Derrida on Metaphor; African SciFi; Traits in Julia; Alternative Japanese Lit; Pulic Key as Address (Snow); Why Information Grows; The Blindness Of The Chilean Elite; Some Victoriagate Links; This Is Why I Left StackOverflow; New TLS Implementation; Maths for Physicists; How I Am 8; 1000 Word Philosophy; Cyberpunk Reading List; Detailed Discussion of Message Dispatch in ParserCombinator Library for Julia; FizzBuzz in Julia w Dependent Types; kokko - Design Shop in Osaka; Summary of Greece, Currently; LLVM and GPUs; See Also; Schoolgirl Groyps (Maths); Japanese Lit; Another Example - Modular Arithmetic; Music from United; Python 2 and 3 compatible alternative.; Read Agatha Christie for the Plot; A Constructive Look at TempleOS; Music Thread w Many Recommendations; Fixed Version; A Useful Julia Macro To Define Equality And Hash; k3b cdrom access, OpenSuse 13.1; Week 2; From outside, the UK looks less than stellar; Huge Fonts in VirtualBox; Keen - Complex Emergencies; The Fallen of World War II; Some Spanish Fiction; Calling C From Fortran 95; Bjork DJ Set; Z3 Example With Python; Week 1; Useful Guide To Starting With IJulia; UK Election + Media; Review: Reinventing Organizations; Inline Assembly With Julia / LLVM; Against the definition of types; Dumb Crypto Paper; The Search For Quasi-Periodicity...; Is There An Alternative To Processing?; CARDIAC (CARDboard Illustrative Aid to Computation); The Bolivian Case Against Chile At The Hague; Clear, Cogent Economic Arguments For Immigration; A Program To Say If I Am Working; Decent Cards For Ill People; New Photo; Luksic And Barrick Gold; President Bachelet's Speech; Baltimore Primer; libxml2 Parsing Stream; configure.ac Recipe For Library Path; The Davalos Affair For Idiots; Not The Onion: Google Fireside Chat w Kissinger; Bicycle Wheels, Inertia, and Energy; Another Tax Fraud; Google's Borg; A Verion That Redirects To Local HTTP Server; Spanish Accents For Idiots; Aluminium Cans; Advice on Spray Painting; Female View of Online Chat From a Male; UX Reading List; S4 Subgroups - Geometric Interpretation; Fucking Email; The SQM Affair For Idiots; Using Kolmogorov Complexity; Oblique Strategies in bash; Curses Tools; Markov Chain Monte Carlo Without all the Bullshit; Email Para Matias Godoy Mercado; The Penta Affair For Idiots; Example Code To Create numpy Array in C; Good Article on Bias in Graphic Design (NYTimes); Do You Backup github?

© 2006-2015 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