Chartio develops non-blocking MySQL queries using Tornado

Re:Chartio develops non-blocking MySQL queries using Tornado by tptacek on Friday June 10, 2011 @03:57PM (#2642186)

You appear only to have read the first graf of this post, as the whole point of eventing the database access layer is to eliminate the "slow query blocks" problem.

But that's not why I'm commenting. Rather:

You're able to make that last assertion only by shifting the meaning of the word "shared" and denuding it of all its concurrency implications. Yes, event systems "share" the event loop, in all the glory of the word "shared". However, no two contexts in an evented system ever step on each other for access to a shared resource.

[ Parent | on HN ]

Re:Chartio develops non-blocking MySQL queries using Tornado by jamesaguilar on Friday June 10, 2011 @04:03PM (#2642210)

> You appear only to have read the first graf of this post

I read a little more than that, but I commented on what was interesting to me. If I'm reading the rest of it right, it's basically a tutorial on making a python extension for two specific mysql API functions. That's fine, but it's not that interesting (to me).

> However, no two contexts in an evented system ever step on each other for access to a shared resource.

Isn't that exactly what is happening when other requests are blocked by a blocking mysql call? They are stepping on each other for access to the shared event thread resource, which they need concurrent access to. Is this not the case? Please help me understand if I am misreading you.

[ Parent | on HN ]