What I have read in the mysql discussion groups is that calling mysql_thread_start allocates some sort of local variables for use in a thread to prevent access contention. This is different from what the actual documentation says. I also have heard folks on the discussion complain about performance hits from using mysql_thread_start: some mutex locking for example that halt all mysqlclient calls while any thread is in the mysql_thread_start function. This indicates to me that there is more to it than the mysql documentation states. It would be great if some one with mysql source code experience could clarify what is really going on!!!
Thanks, Ethan... > I've had a brief look at the MySQL docs. As far as I understand the > situation, calling mysql_thread_start() explicitly should not be required at > all, and calling mysql_thread_end() only once, just before your app > terminates the thread. I reckon it would make more sense to add a libdbi > function for that purpose. Does anyone know how other client libraries handle > threading issues? Do other libs require calling init or end routines in > threads? Needless to say, in drivers which do not support threading this new > function would be a no-op. > > regards, > Markus ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Libdbi-drivers-devel mailing list Libdbi-drivers-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-drivers-devel
