* It is a large key-value pair table (approaching ~ 1 bn rows) with an MD5 key and JSON for value. The look ups depend on the business logic but are necessary. Nevertheless, there are no more than 10-12 queries executed by combining key look ups using WHERE IN queries and pg is surprisingly good with IN queries.
Sunday, June 14, 2015
Re: Scaling/Parallel patterns for a View executing complex database transaction
On May 14, 2015, at 10:30 PM, Me Sulphur <mesulphur@gmail.com> wrote:
If this is the case, then I strongly recommend switching to a NoSQL DB. You aren't using any of the Django ORM functionality, so there's no need to switch to django-nonrel. Almost all of them are faster at key/value returns than PostgreSQL.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment