To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102164
------- Additional comments from [email protected] Fri Sep 18 13:20:43 +0000 2009 ------- @oj: If I understand you correctly, in the use case you describe a new thread is started for every call. Rather than attempting to shave off time from thread creation, wouldn't it be better to eliminate this extensive creation of threads in the first place? After all, even without the context classloader code, thread creation takes time. That the eliminated code is called for every database access does not mean that eliminating it will result in a significant speed increase. It all depends on how much time is wasted elsewhere. Aside from that point, this seems like it is very specific to the database backend. Would it not be possible to treat those threads specially and have their creation path avoid the context classloader setting code, whereas other threads would still use it? And as a bandaid for the current issue, would it not be possible to set the context classloader at least for the non-application-controlled threads such as the event dispatching thread. I really don't think OOo 3.2 can ship if commonly used extensions just break. I think people will much rather live with the database performance they've now had to live with for years. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
