From owner-freebsd-threads@FreeBSD.ORG Mon Aug 11 17:06:44 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0434437B401 for ; Mon, 11 Aug 2003 17:06:44 -0700 (PDT) Received: from letters.cs.ucsb.edu (letters.cs.ucsb.edu [128.111.41.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BE4843F85 for ; Mon, 11 Aug 2003 17:06:43 -0700 (PDT) (envelope-from krishna@cs.ucsb.edu) Received: from ella (ella [128.111.43.201]) by letters.cs.ucsb.edu (8.11.7+Sun/8.11.6) with ESMTP id h7C06gS20766 for ; Mon, 11 Aug 2003 17:06:43 -0700 (PDT) Date: Mon, 11 Aug 2003 17:06:42 -0700 (PDT) From: "Krishna N. Ramachandran" X-Sender: krishna@ella To: threads@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: benchmarks? recommendations for app developers? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Aug 2003 00:06:44 -0000 Hi, I am interested in running a few benchmark tests to gauge the performance of libc_r, lkse, and libthr under FreeBSD 5.1. Specifically, I am interested in benchmarking thread management and synchronization management in the thread libraries. Are there any freely available tools that can do this for me? Also, would you know of some recorded performance comparisons out there that I can look up? Also, I wonder if there are any recommendations as to which library to use for a particular class of application? For instance, if an app creates only 5-10 threads, would it be better to use libThr over KSE? If an app creates 1000s of threads, would it be best to use KSE? I know this question isn't very concrete and has probably been covered many times in bits-and-pieces on the mailing list, but it would certainly help app-developers if a design ideology/principle doc is put up somewhere. Thank you in advance, Krishna p.s. Sorry, if this email turns out to be a duplicate. The previous one i sent has still not made it to the group.