Looks like IO issues. RocksDB is intended to run on SDD drives, much slower on HDD.
Le mar. 27 oct. 2020 à 22:00, Giselle Van Dongen <giselle...@gmail.com> a écrit : > Hi all, > > We have a Kafka Streams application which is showing high CPU usage. When > profiling the application we see that many of the hotspots are related to > RocksDB: flush, seek0, put iteratorCF and get methods. > > We are using the default configuration for RocksDB. We read the > documentation but would like to ask some pointers in case CPU is the > bottleneck. > > We do a join and window step in our code. Commit interval is 1 second and > we have caching enabled and the max cache size is 512MB. We have 5 > instances (6 CPU, 30 GB RAM). > > Thank you! > > > -- *Nicolas Carlot* Lead dev | | nicolas.car...@chronopost.fr *Veuillez noter qu'à partir du 20 mai, le siège Chronopost déménage. La nouvelle adresse est : 3 boulevard Romain Rolland 75014 Paris* [image: Logo Chronopost] | chronopost.fr <http://www.chronopost.fr/> Suivez nous sur Facebook <https://fr-fr.facebook.com/chronopost> et Twitter <https://twitter.com/chronopost>. [image: DPD Group]
