Skip to Main Content
Talk Intermediate

The curious case of MongoDB cache evictions

Review Pending
Session Description

At Gojek, we have a love-hate kinda relationship with document stores. In one such use case, the design of our entity model made sense that a document store (ahem, mongoDb) should be used. Now serving a write traffic of a whopping ~25k RPM, we were bound to hit a wall, and we ended up hitting a cache eviction wall.


This talk explores our debugging process of the issue and all the insights regarding the storage engine which I gathered while deep-diving mongo's source code at v6.0.


By the end of the talk, the participants would appreciate the nuances regarding:

  • How does the storage engine store data?
  • Internals of cache loading and evictions within mongo's storage engine.
  • How to tune your write-heavy database to solve this problem (unfortunately not covered in attached blog post).


References

Session Categories

FOSS

Speakers

Uddeshya Singh Software Engineer Backend (L2) | Gojek

I am Uddeshya Singh (XMediumLinkedIn), SDE-2 Backend at Gojek. I specialize in payments in my 9-5 and have been an avid distributed systems + database geek. I love to tinker with databases and try to break them in my local setup :D, in the event I am successful in breaking or optimizing it, I end up raising the fix with the devs (and hence, sporadically contribute to OSS projects every now and then, KVRocks, go-GRPC being a couple of notable mentions.

Uddeshya Singh

Reviews

No reviews yet.