Hi Vladyslav, this sounds like a worst-case scenario for the Framing stages: 45M lines and each line 2-3 characters long will put a lot of pressure on the streams infrastructure and the framing stage. It might still make sense to benchmark and optimize the Framing stage. One optimization could be to collect a few elements in one go (the current implementation only looks for one match at a time).
Johannes On Wednesday, October 19, 2016 at 4:11:29 PM UTC+2, vladysla...@rtsmunity.com wrote: > > > After some playing with JMC and async boundaries it turned out the hottest > methods are related to ByteString splitting and delimiting (for example, > scala.collection.IndexedSeqOptimized$class.sameElements(IndexedSeqOptimized, > GenIterable) takes 73-75% of processor time). The input file is 45M lines, > 2-3-characters each. Is it at all possible to make this work? > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
