[omniORB] omniOTS Scalability
Scott Robertson
srobertson at codeit.com
Mon Mar 14 11:19:03 GMT 2005
We're aware of that particular issue, but in the two years of production
it hasn't bitten us yet.
I've started work awhile ago on a better way to rollback transactions in
TransactionServer/TransactionReaper.py but it hasn't been a priority for
us yet.
Would you be willing to share you changes?
On Mon, 2005-03-14 at 11:30 +1100, Luke Deller wrote:
> We also noticed a scalability issue with the transaction server: a new
> thread is created for each transaction, to wait for the transaction
> timeout. This allows only a few hundred concurrent transactions due to
> system limits on the number of threads. We have adjusted this code to
> use a single thread for waiting for timeouts. Only when a timeout
> actually occurs does it start a new thread to perform the transaction
> rollback. I'm not sure if this is still an issue with your new version
> though.
>
--
Scott Robertson <srobertson at codeit.com>
More information about the omniORB-list
mailing list