home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   SYNC_SYSOPS      Synchronet Multinode BBS Software Suppor      33,243 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 32,157 of 33,243   
   deon to Gamgee   
   I don't get it   
   24 Jun 25 08:23:19   
   
   TZUTC: 1000   
   MSGID: 13260.dove-syncops@12:1/2 2cbf3da3   
   REPLY: 58243.sync_sys@1:103/705 2cbf6b3b   
   PID: Synchronet 3.21a-Linux master/7276d373a Jun 01 2025 GCC 10.2.1   
   TID: SBBSecho 3.28-Linux master/a43ca30ea Jun 18 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: ALTERANT   
   CHRS: CP437 2   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: I don't get it   
     By: Gamgee to nelgin on Mon Jun 23 2025 07:52 am   
      
   Howdy,   
      
    >  > top - 02:53:43 up 27 days, 12:08,  1 user,  load average: 60.40, 26.47,   
    >   
    >  > 124% cpu is nothing unusual. I have 4 cpus. There's no real reason for   
    >  > the system to behitting a 60 load average.   
    >   
    > With 4 CPUs, a load average of 4.0 indicates that all 4 CPUs are at 100%   
    > capacity.  The 60 indicates that there are a *LOT* of process waiting for   
    > their turn in the queue for CPU attention.  It's almost not possible to be   
    > that overloaded.  Better check the cooling system on those CPUs...   
      
   Actually not completely accurate.   
      
   The load average is a measure of processes who "didnt" get the CPU when they   
   were scheduled to use it. Its possible to have load average above number of   
   CPUs, because of other reasons - the most common I've seen is disk I/O (and   
   the CPU's could be fairly idle).   
      
   Given your swap is full, and your memory utilisation is high, I'm guessing   
   your system is thrashing - spending too much time swapping memory pages in and   
   out (for the processes that want to run), only to swap them back out again   
   when that processes time is up - causing that process (or the next one) to   
   miss it's CPU time slot.   
      
   Your load average can also climb high because of disk errors, where the kernel   
   spends too much time on a blocked read (I/O error), and thus scheduled   
   processes miss their slot.   
      
      
   ...лоеп   
      
   ---   
    ю Synchronet ю AnsiTEX bringing back videotex but with ANSI   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/13 705 105/81 106/201 124/5016 128/187 129/14 153/757   
   SEEN-BY: 153/7715 154/10 30 110 203/0 218/700 221/0 226/30 227/114   
   SEEN-BY: 229/110 114 206 317 400 426 428 470 550 700 705 240/1120   
   SEEN-BY: 240/5832 263/1 266/512 280/464 5003 5006 291/111 292/8125   
   SEEN-BY: 301/1 320/219 322/757 341/66 234 342/200 396/45 423/120 460/58   
   SEEN-BY: 460/256 1124 467/888 633/280 712/848 770/1 902/26 5020/400   
   SEEN-BY: 5020/8912 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca