Re:Twitter's UID associated to each tweet will very soon exc...
by drawkbox on Tuesday June 09, 2009 @03:01PM
(#649674)
Always use a UUID or GUID (same thing) in todays web applications. When we get to terrabytes of data as the norm for apps int based keys are going to seem so ancient.
Sure it takes more room but space it cheap, and it makes syncing and distributed databases so much easier (not tied to one machine or cluster)
Re:Twitter's UID associated to each tweet will very soon exc...
by patio11 on Tuesday June 09, 2009 @08:54AM
(#648960)
I suspect for a lot of people coding against Twitter the notion of integers being signed or unsigned is about as foreign to their experience as pointer arithmetic. I do not consider that a bad thing.
irb > "2,147,483,647".gsub(",","").to_i + 1
2147483648
(Forgive the extra code necessary to strip out the commas. The Windows irb console leaves a little to be desired in terms of midline editing.)
Re:Twitter's UID associated to each tweet will very soon exc...
by tjogin on Tuesday June 09, 2009 @08:03AM
(#648910)
It's such a low barrier of entry and almost non-existant learning curve to code for Twitter, so I expect quite a lot of services to have made that mistake. Not the big ones, though.
Re:Twitter's UID associated to each tweet will very soon exc...
by IsaacL on Tuesday June 09, 2009 @01:07PM
(#649408)
"Values updated every 5 minutes". Looking at the source (I don't actually know JavaScript, but it seems pretty simple) I'm assuming that means they get the current TwitID AND the current rate of increase.
Re:Twitter's UID associated to each tweet will very soon exc...
by thristian on Tuesday June 09, 2009 @06:32AM
(#648840)
To be fair, they say "For some of your favorite third-party Twitter services not designed to handle such a case..." rather than accusing Twitter themselves of primary-key ineptitude.
Re:Twitter's UID associated to each tweet will very soon exc...
by sanj on Tuesday June 09, 2009 @10:16AM
(#649102)
Assuming that Rails is still interacting with the DB, and the ID in question is the primary key (ie, the 'id' on the 'twits' table) isn't quite that easy.
I had to do this a couple of years back when I realized I had a table that'd grow quickly:
Re:Twitter's UID associated to each tweet will very soon exc...
by karanbhangui on Tuesday June 09, 2009 @01:28PM
(#649445)
I'm actually interested in this answer as well. I know of a company using a proprietary db and now that their growth has literally exploded, they're stuck with it.
Re:Twitter's UID associated to each tweet will very soon exc...
by hugothefrog on Tuesday June 09, 2009 @06:01AM
(#648820)
I'd also expect most of those numbers not to be used. Their db writes are probably not contending on one monotonic counter. They're probably using some numbering scheme which guarantees uniqueness across multiple writable databases, but not global serialisation based on id.
Re:Twitter's UID associated to each tweet will very soon exc...
by bretthoerner on Tuesday June 09, 2009 @08:34AM
(#648933)
I'm not sure how they'd be doing that and still giving each tweet a number so close to all the others. I have no idea where you see a "public timeline" as people mentioned above, so I just did a search for "i"... the following tweets were about a second apart.
2088840357 2088840362 (difference of 5, and that's without a real public timeline where you could easily prove each tweet takes the next number in a sequence)
So it isn't as if they're using UUIDs or something unique... they very much seem to be relying on a single counter (currently).
Re:Twitter's UID associated to each tweet will very soon exc...
by hugothefrog on Tuesday June 09, 2009 @08:47AM
(#648953)
For a first guess, if there were 5 writing dbs, each could write every 5th id, starting at a different index (0,1,2,3,4).
You'd end up with globally unique ids, and as long as your writes were (approx.) evenly distributed, all 5 sequences would be (approx.) close to each other.
Who knows, they might have 100 writable dbs, with only 70% up at any point in time, meaning only 70% of all integers are actually used.. anyway, I don't know, I can just imagine them doing something like this if they wanted certain things from the system.
Sure it takes more room but space it cheap, and it makes syncing and distributed databases so much easier (not tied to one machine or cluster)
http://www.sqlite.org/faq.html
What is the point of creating a website like this?
"3 the average tweets per second and the Twitpocalypse date are a rough approximation, please do not schedule any vacation around that date"
irb > "2,147,483,647".gsub(",","").to_i + 1
2147483648
(Forgive the extra code necessary to strip out the commas. The Windows irb console leaves a little to be desired in terms of midline editing.)
irb(main):002:0> 2_147_483_647 + 1
=> 2147483648
"Twitter is seeing about 200 tweets per second, during peak loads. - Robert Scoble"
Note "during peak loads", so 83 is probably not too far off.
2 at a rate of 151 tweets per seconds
http://twitter.com/twitterapi/status/2048659057
There, fixed, send check for $20 to [email protected]
Call me back when they reach 18446744073709551615
I had to do this a couple of years back when I realized I had a table that'd grow quickly:
http://snippets.dzone.com/posts/show/4422
Feel free to send the donation to the same place.
You just made my day. I haven't laughed so hard in ages ;)
But then you would have had 64 bit ID by default anyway.
I wonder what proportion of the total is human-typed, and how much is machine generated?
Two billion tweets would be 1M people posting 2k tweets each, or 100M people posting 20 tweets each.
http://news.ycombinator.com/item?id=648725
"Just 10% of Twitter users generate more than 90% of the content, a Harvard study of 300,000 users found."
I'd expect most of it is machine generated.
2088840357 2088840362 (difference of 5, and that's without a real public timeline where you could easily prove each tweet takes the next number in a sequence)
So it isn't as if they're using UUIDs or something unique... they very much seem to be relying on a single counter (currently).
You'd end up with globally unique ids, and as long as your writes were (approx.) evenly distributed, all 5 sequences would be (approx.) close to each other.
Who knows, they might have 100 writable dbs, with only 70% up at any point in time, meaning only 70% of all integers are actually used.. anyway, I don't know, I can just imagine them doing something like this if they wanted certain things from the system.
Note that one can delete a message, which could explain some gaps.