| Title: | DCE Product Information |
| Notice: | Kit Info - See 2.*-4.* |
| Moderator: | TUXEDO::MAZZAFERRO |
| Created: | Fri Jun 26 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2269 |
| Total number of notes: | 10003 |
Our customer, Optus Communications, wants to know a formula to predict the number of threads to expect per process. The application is single-threaded but uses DCE for security, and CDS for a repository. The customer says that he observes about 8 threqads per application process. He needs to know the upper limits of this for his scalability planning.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2186.1 | Can anyone give us some info here ? | OZROCK::THOMAN | Bring back "Eddie The Eagle Edwards" !! | Mon Mar 24 1997 22:23 | 5 |
Thanks Craig. | |||||
| 2186.2 | no one really knows? | TUXEDO::ZEE | There you go. | Fri Mar 28 1997 15:20 | 9 |
Since DCE components call each other frequently, some procedures create threads as a side-effect. In general, your first CDS or security API call will initialize several threads in RPC, and CDS will create several as well (not sure about security). So, 8 threads is very reasonable once you are running. Since the application is single-threaded, additional CDS threads are unlikely. For planning purposes, 10 would be fine, unless you want a larger fudge factor. --Roger | |||||