Rezultati pretraživanja
  1. 9. lis 2019.
    Odgovor korisnicima

    Yes, I did. It gave me just the parameter for the number of queues. I did run tests on my own. Queue depth of 32 was a sweet spot for this setup. I've also used it in . I did run the test with queue depth of 128 and got similar results.

  2. 9. lis 2019.

    I've done some comparative tests against . ScyllaDB did a great job bounding latencies due to their advanced I/O scheduler (I guess). shows 5x improvement. For more information, take a look at

  3. 6. lis 2019.

    Just to keep things in perspective, inserting 10B keys in took ~14h. Other databases would take dozens of days just to complete this test ;) At an insert rate of 200k keys/s, things look a bit erratic. Normal productions should see lower per cpu rates.

    Prikaži ovu nit
  4. 18. ruj 2019.

Č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.