T.R | Title | User | Personal Name | Date | Lines |
---|
1043.1 | See also MVBLAB::ALPHASERVER_4100 note 583 | NPSS::GLASER | Steve Glaser DTN 226-7212 LKG1-2/W6 (G17) | Tue May 06 1997 17:19 | 6 |
| See also MVBLAB::ALPHASERVER_4100 note 583.
No solution there either, but it's a similar situation (2 processors
running slower than 1 when using named pipes under NT).
It might even be the same customer.
|
1043.2 | Question about app | wagtake.zso.dec.com::wagner | | Wed May 07 1997 14:16 | 5 |
| One question: Is there an attempt to pipeline the send/receive?
In other words, does the client attempt to send another 8 bytes
before getting the reply from the server for the previous 8
bytes?
|
1043.3 | Named Pipes/SMP | NNTPD::"[email protected]" | Genne Roger | Thu May 15 1997 16:20 | 10 |
| No, according to the writter of this Visual C++ app. We wait for the reply
back from the server. It is all a moot point now, because the customer has
decided not to try and fix his code, but to run the app on Sun. The consensus
from a number of folks around Digital was that this was an app problem and
that the customer needed to expend more resource to make it work on NT/SMP.
Much of the basis for this statement was that the app behaved the same way on
Intel, and that programs like SQL do scale reasonably on Alpha as well as
Intel.
[Posted by WWW Notes gateway]
|
1043.4 | Huh? | wagtake.zso.dec.com::wagner | | Mon May 19 1997 20:37 | 6 |
| I might be missing something, but how are they expecting
multiple CPUs to help in what is, essentially, a single
threaded application.
Dave Wagner
|
1043.5 | | KEIKI::WHITE | MIN(2�,FWIW) | Mon May 19 1997 22:58 | 4 |
|
One wonders if they even tried multiple clients?
Bill
|