I don't know what you are trying to look for, but if you are just trying to get a sense of what's stored in the JVM thread dump. Things that strike me as useful are: runnable and locked. For example, too many runnables will give the CPU a workout, and threads waiting on common locks might be dead locked.
You cannot really get a lot of profiling information out of thread dumps. They are in essence, a snap shot of what each thread is doing at the time you signaled SIGQUIT.
In our shop, the development team uses JProfiler to debug WebLogic performance issues. However, it is not free, thus requires a license to use.
