Tweetovi
- Tweetovi, trenutna stranica.
- Tweetovi i odgovori
- Medijski sadržaj
Blokirali ste korisnika/cu @ZebaHrvoje
Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @ZebaHrvoje
-
Hrvoje Zeba proslijedio/la je Tweet
A while back I wrote an internal note on why you can sometimes see discrepancies between application IO sizes and what is observed on the device side. Figured the greater public might want to read it as well, so here it is: "When 2MB turns into 512KB" https://kernel.dk/when-2mb-turns-into-512k.pdf …
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Hrvoje Zeba proslijedio/la je TweetHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Hrvoje Zeba proslijedio/la je Tweet
Posted the initial version of support for IORING_OP_LINK_TIMEOUT commands. They allow tying a timeout to a given request, which will then cancel if not completed before the timeout. More details in the posting below: https://lore.kernel.org/io-uring/20191105211130.6130-1-axboe@kernel.dk/ … and tests: https://git.kernel.dk/cgit/liburing/commit/?id=bc1bd5e97e2c758d6fd975bd35843b9b2c770c5a …
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Hrvoje Zeba proslijedio/la je Tweet
By popular demand, here's support for cancellation of any pending request that has been offloaded to async context. I do have a test case for liburing, I'll be posting that tomorrow. For now, the commit message below has all the details. http://git.kernel.dk/cgit/linux-block/commit/?h=for-5.5/io_uring-test&id=c6e3a0d803b871436fc2385e25dd1e56f7f1dea5 …
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Hrvoje Zeba proslijedio/la je Tweet
Spend a few days starting the workqueue replacement for io_uring. Reasons for this work is stated in the commit message. Next stable, thorough testing, and then syslets/threadlets await (who doesn't love a good pun). http://git.kernel.dk/cgit/linux-block/commit/?h=for-5.5/io_uring-wq&id=f27f11bf017ca5918ab91b63aa146fbb053c7558 …
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
I've done some comparative tests against
#scylladb. ScyllaDB did a great job bounding latencies due to their advanced I/O scheduler (I guess).#tyrdb shows 5x improvement. For more information, take a look at https://github.com/hzeba/benchmarks …#bigdata#databasespic.twitter.com/qTxrkJbheW
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Last thing left to do was to run another 100M keys insert at 10k keys/s on top of 10.1B already inserted keys while running 16 readers to see how things scale. Checkout the results. Also, checkout the reader response tails after the writer finishes ;)pic.twitter.com/NR6WBb4mIf
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
After the last test, I tried inserting 100M keys on top of existing 10B at the rate of 10k keys/s. This time, both the writer and the readers (two of them) were extreamely stable with readers averaging under 0.8ms responses.pic.twitter.com/QPGWfjnRsX
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Just to keep things in perspective, inserting 10B keys in
#tyrdb 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.#bigdata#databasespic.twitter.com/iZpAcb77SJ
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Hrvoje Zeba proslijedio/la je Tweet
Killing time on a long flight, doubled the performance of linked SQEs for some conditions. 4GB copy with examples/link-cp goes from: real0m5.272s user0m0.160s sys 0m5.039s to real0m2.374s user0m0.124s sys 0m1.985s http://git.kernel.dk/cgit/linux-block/commit/?h=for-5.5/io_uring&id=4cbb207204e3a8d0494cf62c3f24ae750bae90ab …
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Hrvoje Zeba proslijedio/la je Tweet
That’s exactly right. But you forgot efficient. And scalable.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
I did some digging around mongodb and found a way to use LSM trees as an underlying data structure. Got better results. With it, mongodb ran for ~38h. Also did some work on
#tyrdb to level out update response spikes.#io_uringpic.twitter.com/f3nVloKE7D
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Hrvoje Zeba proslijedio/la je Tweet
Aristotle's Wheel Paradox When you roll a rigid wheel over a distance equal to its circumference you seem to find that the circumferences of the inner (blue) and outer (red) circles are equal.
Can you guess the fallacy?pic.twitter.com/afuaSFRcUgHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Hrvoje Zeba proslijedio/la je Tweet
Sneak peek from my
@KernelRecipes slides - basic peak perf testing with aio, io_uring, and polled io_uring. Single core. Get wrecked, aio.pic.twitter.com/IsCeiU4riO
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi -
Another view of the data from the test we ran last week
#io_uring@axboepic.twitter.com/cX6AH9gdK5
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
Č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.