From: Serge K. <se...@lo...> - 2006-11-28 20:27:28
|
Yeah, I was thinking of just coming up a with "ThreadGrouper" tool that would take thread names and convert them to a generic name. So resin-21738 \ resin-21737 |---- resin request handler resin-21734 / Store org.hibernate.cache.StandardQueryCache Expiry Thread Store org.hibernate.cache.StandardQueryCache Spool Thread Store org.hibernate.cache.UpdateTimestampsCache Expiry Thread Store org.hibernate.cache.UpdateTimestampsCache Spool Thread are ehcache threads Timer-0 -> java.util.Timer thread resin-tcp-connection-*:9080-13 -> resin tcp handler threads DefaultQuartzScheduler_QuartzSchedulerThread DefaultQuartzScheduler_Worker-9 DefaultQuartzScheduler_Worker-8 are quartz threads resin-thread-scheduler resin-thread-launcher resin-alarm are resin system threads Low Memory Detector CompilerThread1 CompilerThread0 AdapterThread Signal Dispatcher Finalizer Reference Handler main VM Thread GC task thread#0 (ParallelGC) GC task thread#1 (ParallelGC) VM Periodic Task Thread are JVM threads This could then get used in a number of places aside from a report to show the various groupings. -- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. se...@lo... Nate McCall wrote: > Im thinking common patterns with an "other" category would be the way to > go. Grouping in general would be super helpful. What is the Wiley tool > to which you refer? > > Anything that is consistently delineated is parse-able by sed/awk as far > as I'm concerned. We need only be consistent in what style we use for > presentation (style in the sense of 'all tables have headers' more so > than green vs. blue or what have you). > > -N > > Serge Knystautas wrote: >> I'm using email as a surrogate for a real issue tracker. >> >> One thing I found extremely helpful with Wiley's tool was that it showed >> you the # of threads by type of threads. What this means is it would >> show something like this: >> >> Resin TCP threads: 120 >> EHCache expiry threads: 82 >> EHCache spool threads: 82 >> >> I'm not sure the best way to code this... do we develop common patterns >> to aggregate threads with similar names, or do we just use a simple >> string similarity comparison that says any threads named mostly similar >> are in the same group. >> >> This code would get rolled into a simple servlet that would output >> something human readable and easy to parse with awk/sed/etc.... On this >> last point, I'm going to make an optional flag to pass to the active >> connection filter that makes it parseable by awk/sed/etc... The current >> one is intentionally written to be XML parser friendly, but still not >> quite as convenient. >> > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Javascales-devel mailing list > Jav...@li... > https://lists.sourceforge.net/lists/listinfo/javascales-devel |