Do you think that MongoDB would perform well on a shared environment like a Linode VPS? Does MongoDB have any sort of resource gotchas like "oh, you need at least 512MB RAM for the thing to even start up" or the like?
513 karma · joined March 23, 2009
Do you think that MongoDB would perform well on a shared environment like a Linode VPS? Does MongoDB have any sort of resource gotchas like "oh, you need at least 512MB RAM for the thing to even start up" or the like?
Rare as a Himalayan Snowcock spotting!
Results 1 - 10 of 10 for flockdb
Wow. I'd like to know more about it too.Since no one asked, I haven't really truly considered Slicehost an option for my projects. When I started researching the various options, Linode looked 2nd best by the numbers for VPS. prgmr.com looks the best but I am not sure I'd bet the farm on such a tiny operation. Slicehost is of course similar to Linode but it seems Linode gives you more bang for your buck and has nothing to do with Rackspace which in my limited foray into this hosting world seems like a good thing (but what do I know?).
While I can get good dedicated server deals they are still too expensive to me. So I'm diving in deep to learn how to create a almost pure scale-out solution based on a larger (than dedicated) number of VPS instances. Something like
inexpensive+commodity+more ≥ expensive+powerful+fewer
I really want to be able to have a script that watches load and dynamically adds more capacity. I'm not a fan of calling this "cloud" based but the ideas are pretty similar.Good luck with your project! BTW, have you looked at Neo4j (which is a graph database that seems to get high marks)?
We do not keep any servers unused, all servers are recycled
and added to queue so the customers have equal rights to get
them... and we cannot keep them reserved because of the costs...
instead you should consider leasing them for longer periods
so you have them available.I suppose a system where data could be lost if buffered in RAM for up to 30s could replicate to other hosts in the cluster with the (perhaps naïve) intuition that the probability of > 1 hosts going down within the same 30s interval is low -- "someone's got the data somewhere!". Of course, if they are on the same source of power... :)
One could use a consistent hashing scheme as employed in Riak and others for read operations in such a setup and thus be a bit more fault-tolerant (hand waving a bit).
This is without any hard-earned experience with this other than reading... Thoughts?
Keys in the document values are stored in the document. Big keys = more space required.
No async client drivers (still true? The last time I surveyed was in November)
"It doesn't support rollback or anything like that, so you'd have to do that yourself."
Smaller problems or non-problems:
It is not durable (writes every N seconds). Granted, most "NOSQL" experiments are not strictly durable (e.g. Redis, Tokyo Cabinet, etc.)
4MB limit / document (I don't have values this large anyway)
32-bit host limits MongoDB DBs to 2GB total size (so use 64-bit)
Auto-sharding is in alpha, and I'm glad to see it coming. But, things like this scare me: "If a shard is down, the query will return an error." Compare that feature to something like Riak wherein multiple copies of values are stored (Riak's W, DW parameters). MongoDB with auto-sharding does not seem fault tolerant. Am I missing something on this?
Please let me know your thoughts as I do like MongoDB for its speed and query operators but the above concerns me.
http://searchyc.com/%2522ask+hn%2522+vps
I like Linode FWIW. Bandwidth pooling, good API, good resources, mostly-idle (hand-waving) quad-cores, 5 data centers, a very responsive IRC channel and forums, ability to grow/resize a linode at any time, etc.
Request-response, XHR, long-polling, "COMET" (blarg, I hate that moniker) when talking to the backend?
Maybe I'm insane or overly optimistic or both. Designing things to bend and not break is really difficult and time consuming. "Thanks Captain Obvious! You are so insightful!" No, I know, but I'm going through the cutting-of-teeth ritual now so these kinds of things are on my mind.
I suppose a more modern version of WOPR might simulate WoW.
Number of players?
ONE MILLION SEVEN HUNDRED THOUSAND FIVE HUNDRED FORTY TWO
Initializing...
http://www.youtube.com/watch?v=NHWjlCaIrQoDid you pull this out of thin air?
The number of things that go wrong with their text cum HTML editor does double every year (EN for OS X)!
It's really quite poorly implemented. Plain text suddenly transmogrifies into bold text with a different font, deleting a CRLF causes the current paragraph to randomly have double-spaced lines, etc.
$68K per month blows my mind if the number represents monthly expenses instead of yearly given the number of active users. I've an iPhone game with over 3MM active unique users and by my math I can host a multiplayer solution for less than $800/month. Granted, my service will not be sending giant PDFs, notes, voice memos, etc. but still... What am I missing? I am not being snarky. I need to learn.
Also, is the 4 ops guys per 60 servers a non-shocking number? When I worked at Yahoo, the ratio of ops staff count to production server count was IMHO ridiculously high and I never understood why it was required. Sure, some redundancy and so on. Clearly I'm missing something though - what?
I'm eager to correct my misunderstandings if I'm the one off base here. Can you recommend where I might find similar (perhaps more detailed) descriptions of production environments by other companies?
This looks like interesting research: http://www.squicky.org/work/sca07gtw/
Anyone know much about motion capture? Is it something that is now doable at any sort of homebrew budget levels nowadays?