Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTSRV-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Menu
LISTSERV Archives LISTSERV Archives
LSTSRV-L Home LSTSRV-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Proportional Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
New SIGNUP FILE handling in 1.5m
From:
Eric Thomas <ERIC@FRECP11>
Reply To:
The Revised LISTSERV Distribution List <LSTSRV-L@DEARN>
Date:
Tue, 17 Nov 1987 21:27 SET
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
To avoid  storage fragmentation,  the SIGNUP  FILE will no  longer be  kept in
GLOBALV  storage.  The complete  file  will  be  held in  LSVFILER  file-cache
storage, which takes about  30% less storage and results in  only one chunk of
DMSFREE storage being allocated instead of N (where N is 1650 at FRECP11, 2200
at CEARN and 4800 at BITNIC). This also speeds up the startup procedure, since
the file no longer has to be loaded into GLOBALV storage. The compression time
(the file must be compressed if it  had been altered) has also been halved, so
that if the file doesn't have to  be compressed, the startup time is zero, and
half what it was before if the file must be rebuilt.
 
Access to  a given  name is  now a  bit slower  (maybe 5  times slower  than a
GLOBALV  call,  but  then  this  is  still <<  the  time  spent  in  the  REXX
instructions :-) ),  and postmasters will be  able to choose not  to cache the
file in  storage at  all if  they so desire.  This would  double the  CPU time
required  to search  something in  it (no  big deal,  0.01/0.02 -->  0.02/0.04
(4381-11) :-) ), but it DOES take more wall clock time to execute. This can be
particularly painful when a  list is PUT and every name  must be accessed, but
on the other  hand it can save you  up to some 200k of  storage (assuming 5000
entries). The default will be to keep the file in storage.
 
  Eric

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV