RFC 450 UNKNOWN NETWORK SERVICES · COMPUTING ACCESS

MULTICS sampling timeout change

A change to the anonymous Multics session time limit.

RFC EDITOR

Padlipsky, M.A., "MULTICS sampling timeout change", RFC 450, DOI 10.17487/RFC0450, February 1973, <https://www.rfc-editor.org/info/rfc450>.

BIBTEX

@misc{rfc450,
  series = {Request for Comments},
  number = 450,
  howpublished = {RFC 450},
  publisher = {RFC Editor},
  doi = {10.17487/RFC0450},
  url = {https://www.rfc-editor.org/info/rfc450},
  author = {M.A. Padlipsky},
  title = {{MULTICS sampling timeout change}},
  pagetotal = 1,
  year = 1973,
  month = feb,
}

PUBLISHED: February 1973
AUTHORS: M.A. Padlipsky
STREAM: Legacy
PREVIOUS LIMIT: 1 CPU minute
NEW LIMIT: 5 CPU minutes
DOI: 10.17487/RFC0450

RFC text

Original text · RFC Editor View on rfc-editor.org ↗

Network Working Group                                   M. Padlipsky
Request for Comments # 450                              MIT-MULTICS
NIC # 14134                                             February 8, 1973



                    MULTICS SAMPLING TIMEOUT CHANGE


In response to popular demand, and in view of the fact that we've found
an extra bit of budget, the timeout on sampling ("anonymous") use of
Multics via the Net has been increased to 5 cpu minutes (from 1 cpu
minute); coupled with various internal speedups, this change should
allow the performance of substantive experiments in a single session.










       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by Alex McKenzie with    ]
       [ support from GTE, formerly BBN Corp.             9/99 ]

ISO Plain Language

On this page

PROBLEMThe time limit for anonymous sampling use of Multics over the network was one CPU minute.

MECHANISMThe limit was increased to five CPU minutes; the RFC also notes internal speedups.

A SERVICE CHANGEThe author says the change should allow substantive experiments in one session.

§1The Previous Time Limit

The RFC says anonymous sampling use of Multics over the network had a timeout of one CPU minute. It describes this as a limit on trial use of the system.

People trying Multics over the network had a one-CPU-minute time limit. The RFC announces a change to that limit.

§2Five CPU Minutes for Sampling

In response to user demand and an extra bit of budget, the timeout was raised to five CPU minutes. The RFC also mentions internal speedups.

The author says these changes should let users carry out substantive experiments in a single session.

The new limit is five CPU minutes instead of one. The author says this and internal speedups should make meaningful experiments possible in one session.

§3What the Notice Covers

RFC 450 is a one-paragraph announcement about the sampling timeout and system speedups. It does not describe a protocol or provide details about the speedups.

This note reports a service change. It does not explain the internal speedups.