On Thu, Feb 26, 2009 at 4:19 PM, Nick Arnett nick.arn...@gmail.com wrote:
A relational database falls down very fast on this kind of analysis. For
example, I have more than 300 followers, which is a simple query... but it
returns 300 users and now the query needs to ask who the followers of
(Privately mailed, since I'm nervous about edging off-topic)
I'm working on some related areas, capturing conversation data from Twitter
at http://twitter.mailana.com/ . My approach has been the classic disk-space
trade off, creating massive indices to pre-cache queries. You're right
though, even
On 2/26/09 7:19 PM, Nick Arnett wrote:
Yes, you probably don't, unless you just want to do it occasionally.
I'm working on some graph manipulations like that... the challenge is
that Twitter is so open that the graphs are enormous for many people.
This isn't a very hard problem on a small
On Thu, Feb 26, 2009 at 5:54 PM, Dossy Shiobara do...@panoptic.com wrote:
On 2/26/09 7:39 PM, Nick Arnett wrote:
FYI, there are 345,000 nodes and 1.4 million edges in the graph of me,
my followers and their followers. I'm sure this could be pared down
considerably by eliminating a handful
On Thu, Feb 26, 2009 at 6:10 PM, Andrew Badera and...@badera.us wrote:
If you're trying to use cheap-a$$ unlimited web hosting in lieu of true
application/cloud/SaaS hosting, sure, 1.4M sounds like a lot.
If you're willing to spend a couple bucks a month, or write Python against
GAE, 1.4M is
