---
title: "Discussion on \"25% of my Rust CLI's runtime was doing work nobody asked for\" | Hashnode"
description: "Discussion on \"25% of my Rust CLI's runtime was doing work nobody asked for\". I expected regex to be the slow part, as that's what everyone says about parsing logs.\nBut profiling my Rust-based log analyzer showed the real culprit was something else. 25% of my CPU runtime was oc"
url: "https://hashnode.com/posts/profiling-a-rust-log-analyzer/6a662606f386eb7bf1da919d"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [25% of my Rust CLI's runtime was doing work nobody asked for](https://omanshchoudhary.hashnode.dev/profiling-a-rust-log-analyzer?utm_source=hashnode&utm_medium=feed)

I expected regex to be the slow part, as that's what everyone says about parsing logs. But profiling my Rust-based log analyzer showed the real culprit was something else. 25% of my CPU runtime was oc

Jul 26 · 11 min read · omanshchoudhary.hashnode.dev  
Read the article

-   [#rust](https://hashnode.com/tag/rust)
-   [#performance](https://hashnode.com/tag/performance)
-   [#optimization](https://hashnode.com/tag/optimization)
-   [#profiling](https://hashnode.com/tag/profiling)

## Written by

[Omansh Choudhary](https://hashnode.com/@omanshchoudhary)

@omanshchoudhary · Delhi, India

  
[View profile](https://hashnode.com/@omanshchoudhary)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
