{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:42:15Z","timestamp":1750308135904,"version":"3.41.0"},"reference-count":0,"publisher":"Association for Computing Machinery (ACM)","issue":"4","license":[{"start":{"date-parts":[[2005,10,1]],"date-time":"2005-10-01T00:00:00Z","timestamp":1128124800000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["SIGOPS Oper. Syst. Rev."],"published-print":{"date-parts":[[2005,10]]},"abstract":"<jats:p>That QoS and Realtime are mutually exclusive is shown by use of simple queuing theory. QoS mechanisms will not be active in the light to moderate (up to 50% average and 80% peak occupancy) communications load regime used by realtime systems, as by definition there is enough communications capacity to satisfy any and all requests in that moderate-load regime. QoS is required only when communications system path occupancy exceeds about 80%, where offered traffic must be forcibly shaped or deferred to fit the insufficient available communications capacity. No realtime system should be designed to operate in that regime, because the resulting large and random-appearing variations in latency make it impossible to achieve realtime behavior, or in many cases, to even achieve stable system operation.<\/jats:p>","DOI":"10.1145\/1088446.1088448","type":"journal-article","created":{"date-parts":[[2005,11,7]],"date-time":"2005-11-07T19:28:32Z","timestamp":1131391712000},"page":"18-22","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":0,"title":["Quality-of-Service versus Realtime"],"prefix":"10.1145","volume":"39","author":[{"given":"Joseph M.","family":"Gwinn","sequence":"first","affiliation":[{"name":"Raytheon Integrated Defense Systems, Sudbury, MA"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2005,10]]},"container-title":["ACM SIGOPS Operating Systems Review"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1088446.1088448","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1088446.1088448","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T16:08:33Z","timestamp":1750262913000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1088446.1088448"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2005,10]]},"references-count":0,"journal-issue":{"issue":"4","published-print":{"date-parts":[[2005,10]]}},"alternative-id":["10.1145\/1088446.1088448"],"URL":"https:\/\/doi.org\/10.1145\/1088446.1088448","relation":{},"ISSN":["0163-5980"],"issn-type":[{"type":"print","value":"0163-5980"}],"subject":[],"published":{"date-parts":[[2005,10]]},"assertion":[{"value":"2005-10-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}