• https://doi.org/10.1145/1413254.1413256Copy DOI Icon

Sizing Your System

  • Jul 1, 2008
  • Queue
  • George Neville-Neil
Show More
  • Abstract
  • Literature Map
  • Similar Papers
Abstract

Dear KV, I’m working on a network server that gets into the situation you called livelock in a previous response to a letter (Queue May/June 2008). Our problem is that our system has only a fixed amount of memory to receive network data, but the system is frequently overwhelmed and can’t make progress. When I ask our application engineers about how much data they expect, the only answer I get is "a lot," which isn’t much help. How can I figure out how to size our systems appropriately?

Similar Papers
  • Conference Article
  • Citations1

Machine Learning based User QoE Evaluation for Video Streaming over Mobile Network

  • Oct 01, 2020
  • Yanhong Zhu +5
  • Book Chapter
  • Citations1

Chapter 15 - A reliable blockchain and edge–cloud architecture for facilitating fault-tolerant IoT applications

  • Jan 01, 2021
  • Blockchain for Smart Cities
  • A Amuthan
  • Conference Article
  • Citations3

Data process and signal analysis based on LabVIEW

  • Aug 01, 2009
  • Liu Yan
  • Conference Article

The development and implementation of MOSAIQ Integration Platform (MIP) based on the radiotherapy workflow

  • Mar 13, 2017
  • Proceedings of SPIE, the International Society for Optical Engineering/Proceedings of SPIE
  • Xin Yang +18
  • Preprint Article

The Open Seismometer Network as a Collaborative P2P Infrastructure that is Scalable, Distributed and Robust

  • Mar 13, 2026
  • Carlos García-Saura +1
  • Conference Article
  • Citations18

TCP-PARIS: a Parallel Download Protocol for Replicas

  • Sep 12, 2005
  • R.P Karrer +1
  • Research Article
  • Citations4

Standard deviation (SD)-based data filtering technique for body sensor network data

  • Jan 01, 2015
  • International Journal of Data Science
  • Basant Tiwari +1
Cactus Communications logo

Copyright 2026 Cactus Communications. All rights reserved.