| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1198.1 | | PSW::WINALSKI | Meetings are our most important product | Sat Jul 29 1989 22:18 | 9 |
| Submitting this batch job on the 3600 ought to work:
$ SET DISPLAY/CREATE/TRANS=DECNET/NODE=ws::
$ RUN SYS$SYSTEM:DECWRITE
where "ws" is the node name for the workstation.
--PSW
|
| 1198.2 | | PRAVDA::JACKSON | Elect Bill Jackson, Newton Ward 1 Alderman | Mon Jul 31 1989 09:31 | 10 |
| Remember, the 3600 has the same CPU power as the workstation, so
more than one DECwrite job is likely to cause your server to page like
crazy (unless it has 64MB of memory) and is also likely to perform
slowly.
DECwrite (as many compount document editors) takes a lot of resources
-bill
|
| 1198.3 | Be Careful | WAV14::SLATTERY | | Mon Jul 31 1989 13:04 | 65 |
|
Be careful, you may end up with an unhappy customer. As the attached
note states, the licensing people don't know how to deal with this
issue and are therefore sitting on the fence for an undetermined
amount of time. I have not seen the official DECwrite SPD so I
don't know how it is handling this issue.
Regards and good luck
Ken Slattery
<<< YUPPIE::DUA1:[NOTES$LIBRARY]SOFTWARE_LICENSING.NOTE;34 >>>
-< Software Licensing Issues >-
================================================================================
Note 33.0 SPD's and use in a client/server model. 1 reply
NOHOPE::GALLOZZI 45 lines 21-JUN-1989 13:17
--------------------------------------------------------------------------------
Date: June 21, 1989
To: Software Product Managers From: Carl Gallozzi
Dept: OS/Software Business Group
Loc : ZK01-3/J33
Net : Blumon:://Nohope::
Subject: Software Product Descriptions and client/server computing model
Background:
-----------
Many Digital software products are being produced to work within the
client/server model. The general software license business rules pertaining
to this area have not as yet been finalized. The current general rules
are that - a VMS based VAXserver system is shipped with a VMS File and
Application Server license which through terms and conditions has an
intent of allowing no interactive 'log ons'. One current interpretation of
this intent is that VAXservers allow no interactive log ons, no screens being
driven by VAXservers [screens DEC/X window terminals being classified as
'users']. The situation is essentially similiar for Ultrix based VAXservers.
This situation is currently under review.
Immediate Problem:
------------------
New applications such as DECwrite V1.0 and others wish to properly grant
rights for use in a client/server model, and delineate them within the
product SPD.
Request:
--------
That, for a short time period until a global policy can be agreed upon, no
software product explicitly specify support for the product's use as 'either
a client or server' upon a VAXserver or VAXstation. All other references
to supported VAX cpus can and should be made. This ambiguity will
accomplish at least two things:
. It will allow the creation of the SPD and shipment to proceed.
. It will not preclude any policy options that Digital may wish to
consider.
Carl Gallozzi
OS/Software Business Group
6/21/89
[EOB
|
| 1198.4 | | JAMMER::JACK | Marty Jack | Mon Jul 31 1989 15:58 | 2 |
| DECwrite is user licensed, so it is a quite different animal.
|
| 1198.5 | Memory hog vs CPU pig | POBOX::KOCH | No matter where you go, there you are. | Tue Aug 08 1989 16:42 | 7 |
| RE .2
After talking to some folks who had done some DECWRITE benchmarking;
It seems that DECWRITE is more of a memory hog than CPU pig. Rule
of thumb is currently 2MB for each DECWRITE user, with 1MB for each
extra 100 document pages. So it seems that a 16MB 3600 could support
6-7 users.
|
| 1198.6 | DECwrite runs better on large shared memory systems. | DWOVAX::YOUNG | in the iron grip of bureaucracy | Wed Aug 09 1989 03:49 | 7 |
| My observations have been similar.
Additionally, I have observed that 25-50% of DECwrites working set is
global, so some economies of scale can be had.
-- barry
|