fehguy

5 ms·

1. 31.▲
   by fehguy 16y ago

   I think there are some possible timing issues with making that a general behavior in the server. 10gen did make it the default behavior on slaves, where the inserts are controlled by the oplog ( http://jira.mongodb.org/browse/SERVER-1646 )
2. 32.▲
   by fehguy 16y ago

   You could run mysql with the memory storage engine and with our schema--which would require multiple outer joins OR subqueries--mongodb will still be much faster. So I think it's much more than an fsync issue.
3. 33.▲
   by fehguy 16y ago

   Storing objects with any sort of hierarchy is so simple with Mongo that the LOC required to do so is ridiculously smaller. Querying them is also faster--for instance we can filter in our dictionary data with queries like {"entry.definition
4. 34.▲
   by fehguy 16y ago

   Querying before the writes solved a lot of problems. It gets the object in the working RAM set. When doing an update, the database gets LOCKED when the statement hits the server--that means if your document is not in memory, you have to w
5. 35.▲
   by fehguy 16y ago

   Hi Christopher, glad you like Wordnik. Do you mean you couldn't find this? http://www.wordnik.com/words/monad
6. 36.▲
   by fehguy 16y ago

   We run one mongod master, one slave (soon to be two slaves). These are used across all the api servers.
7. 37.▲
   by fehguy 16y ago

   That's per api server, we have 4 api servers.