jtdutils / News: Recent posts

Well, I haven't been active on this project for some time as I've been intensively playing Guild Wars, Guitar Hero and The Witcher ;)
But since like two weekends I've been writing a GTK+ GUI as competition to Ingo Rockel's TDA. It'll sure take some time until it reaches a releasable state, but it'll be the 'highlight' of 0.6.

I just released jtdutils in version 0.5. There have been many changes in the release but most of them can't be seen ;). Actually I've refactored many things a couple of times just like it should be when you're learning new things about programming in C. I've also done a few things that may be noticed:
- so much less memory consumption
- major performance upgrade
- man pages!
- a first shot of IBM javacore/thread dump parsing
- tdpager for paging/browsing through thread dumps
- tdprobe (experimental)... read more

I just activated a git repository and been playing around with it. For the next time I'll just commit on git and, if I like it, I'll remove the svn repository.

Yes, it's done. The docs are done, the refactorings are done, and I am done. I think this was the last release that required a giant refactoring, but I guess I said that earlier too. At the moment I'm pretty fine with the code and my plans don't involve any big changes, but some nice new features.

It's been a couple of months now since my last release. I've actually done *major* refactorings and both performance increasements and memory consumption decreasements. I fixed a couple of memory leaks (<3 valgrind) and changed fom my own format to xml, so I can easily reuse the output of tdstrip in future tools, e.g. a plugin for TDA or some other graphical tool I'd prefer to write in java. ... read more

Well. It's been a couple of months when I announced 0.2 while 0.3 contains a couple of more utils and is more atomic now. Less complex functionality in each tool so they can be combined much more flexible. I think it's quite usable now, but there's still much more work needed to achieve a great working toolbox. And I *want* that!

Since I'm not used to the (build-) management of c code my first shot was not very good. Now I hope to fit more into how c code should be 'managed' and went back to what I originally wanted: one tool for one problem. In 0.1 tdstrip was on the path to become very bloated, now it just extracts thread dumps to standard out (including filtering mechanism) so other tools can do the rest. In 0.2 the new tool tdstats was created to print statistics for tdstrip-streams/-dumps. Currently the threads are grouped by their states (running, waiting, sleeping, ...) and you may specify filters to create extra statistics (e.g. all threads matching ^AJP.*$ and all threads matching ^PullPushAdapter.*$). I'm planning to add more tools to handle everything, at least I, need to analyze thread dumps. Maybe I'll even add tools to analyze heap dumps (dominator tree's, etc.) since most of the time I don't need all the functionalities of tools like Eclipse Memory Analyzer (MAT).

I just uploaded the first version of the tool tdstrip which is used to extract thread information from a logfile full of java thread dumps. It supports basic filtering possibilities and is pretty fast with a quite memory usage even on files having many (>1000) thread information.