Viewing profile — rick446
rick446
HN member- Joined
- Fri, Dec 17, 2010, 9:46 PM UTC
- HN karma
- 104
- Public activity
- 17 items
- HN profile
- View on Hacker News ↗
About rick446
No profile information was provided.
Recent public activity
- story
- story
- story
- story
- story
-
comment
Comment #4025421
If they are always under 16MB, you'll be fine, though if you could stream them out of GridFS using a chunked encoding or something like that, you might save a bit of RAM.
- story
-
comment
Comment #3416559
I guess it depends on what % of your writes were simply updating a boolean or integer value. My benchmark shows that simple updates like that don't affect query performance much. W…
-
comment
Comment #3412044
Glad to help! 10gen actually has a policy of never sharing benchmarks so that explains why they never said anything.
- story
- comment
-
comment
Comment #3179107
I guess on an extremely high traffic site running with a relatively small amount of RAM you could cycle through the whole LRU cache in the VM between operations, but I'd expect the…
-
comment
Comment #3178861
Yeah, I guess I should make the point that if you don't put the journal on SSD (and you only need a few gigs of SSD to journal terabytes of spinning disk storage), you will see sig…
-
comment
Comment #3178816
There are a number of MongoDB shared hosts listed at http://www.mongodb.org/display/DOCS/Hosting+Center that you might want to check out.
- comment
-
comment
Comment #3178720
MongoDB has single server durability since 1.8 with the journal. If you put the journal on an SSD, you can even get it almost for free performance-wise.
-
comment
Comment #3178712
Writing does lock the database (or at least the shard), but if the page is in RAM, that means you're locked for the duration of a write to memory, which is inconsequential. The pro…