Pssst...Ferdy is the creator of JungleDragon, an awesome wildlife community. Visit JungleDragon

Thread3r 1.00 released »

FERDY CHRISTANT - JUL 30, 2007 (08:00:19 PM)

I'm very busy currently with my deep dive in the .Net framework, as part of my certification path. This study involves doing lots of practical assignments. Occassionally I come up with my very own assignments, and this time one got out of hand, and ended up in a s3maphor3 project called Thread3r.

Thread3r is a simple diagnostic tool that analyzes the performance benefit of multi-threaded desktop applications over single-threaded applications.

The following article tells you what exactly Thread3r is, where to download it, and how to use it:

Multi-threading on the desktop

As a teaser, here is a screenshot of Thread3r in action:

Don't care about this article? I have dozens of others covering various geeky subjects!

Note: Thread3r comes with a friendly installer from which you can have it running within a minute. I would really appreciate if some of you try it and play around with it.

Comments: 3
Reviews: 1
Average rating:
Highest rating: 4
Lowest rating: 4

COMMENT: TOM

AUG 10, 07:51:17

comment » Nice going there. Just a little annoyance; instead of "Benchmark results (hh:mm:ss.ms): 00:00:07.085" why not output this as "0h0m7.085s" or even better "7.085s". All those leading zeros and separators can become a bit confusing. «

COMMENT: FERDY

AUG 14, 02:22:45 PM

comment » Tom, thanks. There is a reason for those seperators. The time it will take to run depends on two factors: the performance of your hardware, and the number of operations you select. With Thread3r you can easily run a set of operations that takes hours to complete. In those cases there will be no leading zeroes.

-- Ferdy «

COMMENT: TOM

AUG 15, 12:28:37

comment » Hi Ferdy. I agree that you can easily select options that will cause the tool to run for hours and thus need the positions to display these.

My point however was to use "h", "m" and "s" as separators instead of ":", ":" and ".".

It feels to me like more-and-more UI messages that display elapsed/remaining time these days use something like "2d13h25m12.525s" instead of "61:25:12.525" simply because it is more intuitive to understand what the numbers mean (especially if there is a wide range of possible duration to be displayed). «