3 ms·
been playing with RavenDB and throwing twitter data at it... seems very stable taking about 30-50 tweets a second on a VM... think the bottleneck is CPU (hoveri
by tiernano 15y ago
been playing with RavenDB and throwing twitter data at it... seems very stable taking about 30-50 tweets a second on a VM... think the bottleneck is CPU (hovering around 80%)... the VM only has one core dedicated to it currently...
- friendlytuna 15y agoIt seems to be the only .NET-related NoSQL DB that I ever hear very much about. This post is by the creator, Ayende Rahien. Great guy, really smart.
- pestaa 15y agoMy guess is that we're not talking about 7kb of data (50*140) per second, but 30-50 signed, stamped, delivered transactions, right?
- tiernano 15y agoyea, its more than 140 bytes! the average "tweet" object is about 3k, and includes a lot of meta data about the user, the tweet, location, etc... Its direct from the Twitter stream. think there is a bit of overhead of actually parsing the JSON file into a CLR object... since RavenDB actually knows about JSON it may be possible to just give it the data, and see what happens...