Rezultati pretraživanja
  1. 1. lip 2015.

    Dr. Michael Cahill talking about at .

  2. 22. sij 2019.

    Daily standup for team. The tiger comes to you, and you pet the tiger while sharing your update.

  3. 18. ožu 2015.
  4. 22. stu 2014.
  5. 18. sij 2019.

    Visiting the Sydney office, where is created.

    Prikaži ovu nit
  6. 3. lip 2015.

    I could really use compression for packing my luggage after all the swag I picked up at How's it all gonna fit?

  7. 7. tra 2015.

    Reading about very interesting storage engine, how independent will it be for MySQL, etc now it is owned and part of MongoDB?

  8. 3. srp 2015.

    How with can start to stalk the Big Data Analytics Gorillas - 12x faster analytics.

  9. 3. svi 2017.

    On : A deep-dive into the write-ahead log & how an optimization can become a bottleneck:

  10. 20. stu 2015.

    This morning, first tests with 3.2 and : my inserts are 10x faster than with mongo 3.0 (mmap) !!

  11. 7. ožu 2015.

    MongoDB 3.0 production: space usage decreased in 4.3 times and performance read/write increased in 3 times

  12. 13. velj 2015.
  13. 1. lis 2015.

    Is the pluggable storage engine like adding nitrous for your database? . explains...

  14. 26. lip 2016.
  15. 5. velj 2015.

    With tag aware shards and you can have recent data compressed for speed and older data heavily compressed for storage.

  16. 4. tra 2018.

    Great question! Perfect time to mention that storage engine (default since 3.2) doesn't do document locking, it uses lock-free concurrency control mechanisms & (as an example) writes don't block reads because readers are reading previous version of the doc.

  17. 15. ruj 2016.

    Great effort by the Engineering Team and support yesterday after a seamless upgrade to . Zero downtime on .

  18. 16. ožu 2016.

    This morning we’ve upgraded our database infrastructure to use the latest version of all with zero downtime.

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.