Missing DTrace from Solaris for tracing live processes

Anusheel BhushanAnusheel Bhushanco-founder of PlankOriginally posted on LinkedIn 

I miss dtrace from Solaris. Dtrace probes would allow you to attach the trace to live running processes, without needing to restart the process. Some things you could check:

- print which functions are doing memory, disk allocation or network requests incl the sizes. This was great to catch memory leaks or programs with poor cache performance

- trace a specific code function. Using the symbol for the function in the binary, you could print the parameters and function return values

- trace the latency of a user request by tracing invocations of functions at the start/end of the processing

- performance measurement of modules. Attach the probe for an hour and do a running count of how many times a function was called or how much memory was used on average for a request

Linux strace seemed not as powerful. Any other options?

brendangregg.com/dtrace.html

  • Software architecture

Keep reading

Models and researchSoftware architecture

Quantized Llama models make on-device AI apps practical

With the latest quantized Llama models that are just 1.3GB and 3GB in size, you can start doing mobile/desktop apps that download fine tuned models per user/customer and can run fully locally. This makes variable running costs of AI apps zero and moreover achieves maximal data privacy. We are building a few apps with this new awesome architecture. Anyone else doing that? Would love to exchange notes.

Software architecture

When RAG and vector databases are the wrong tool

Common error in app-layer LLM products is that people use RAG and Vector DBs incorrectly. To process a single document or small amount of input information, people first chunk it, throw it in a vectorDB then retrieve it and put in the context. That makes no sense if the original document is small and could literally be fully packaged in the context window. Remember - you need RAG if during inference, you need to select a subset of information from thousands of documents (100s of millions or billions of tokens), which of course is impossible to include in the context window of a single inference.

Software architecture

Eras of software from the mainframe age to AI

I've been reflecting on the evolution of software development and the distinct eras the industry has experienced over the years. For each era, I've considered the defining characteristics, the technological advancements that emerged, and the market segments most affected or newly created by these innovations. Dive deeper into this exploration on how software has transformed from the mainframe age to today's AI-driven landscape. In a follow-up post, I will talk about how the tooling has evolved from assembly languages to high-level languages to now plain-english prompts and agentic pipelines.

Enterprise AI

Business workflow automation and the zero cost of software

Business workflow automation is the dev-tools of business domain just like we had a whole developer tool stack of SaaS serving tech companies. Unfortunately this time, this stack itself will not hold any value since the cost of developing software has gone to zero. So where is the value? It will continue to be in human ingenuity and understanding of how other humans tick. Our economy is based on a barter system of solving each other's problems. Now that the solving of a lot of those will be done by AI, the value shifts to knowing what to solve and finding the people with those problems.

All postsOlder posts