It is not thread pools by itself but more reusing existing thread pools. If you have AOLServer thread pools and Tcl thread pools and if you have 100 connections always connected to the server and using SMTP and HTTP (this is my case) both AOLServer pools and Tcl pools would compete for the same resources. I do not have Tcl implementation, it was more than 1 year ago and i did not save old experimental code.
Dossy Shiobara wrote:
On 2004.08.17, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
Only after i started using AOLServer's thread pools and connection manager, performance issues disappear.
Perhaps I should share code to implement thread pools in pure Tcl? Do you still have your pure Tcl implementation of your SMTP server? Would you be interested in hooking a thread pool implementation up to it and see how it performs?
-- Dossy
-- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70)
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
-- Vlad Seryakov 703 488-2173 office [EMAIL PROTECTED] http://www.crystalballinc.com/vlad/
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
