TID: FMail-lnx64 2.1.0.18-B20170815   
   RFC-X-No-Archive: Yes   
   TZUTC: 0200   
   CHRS: UTF-8 2   
   PID: GED+LNX 1.1.5-b20161221   
   MSGID: 2:280/464 5cbf089f   
   REPLY: 1:1/123.0 5CBE261F   
   Hi Ozz,   
      
   On 2019-04-23 00:37:51, you wrote to mark lewis:   
      
    ON> A while back you had mentioned it took around 30m to process a lot of   
    ON> mail on your system. I am now focusing on tweaking the what I have   
    ON> implemented JAMmb and my PKT parser... current stats from log:   
      
    ON> ------------   Mon 22 Apr 19 ExchangeBBS FTN Tosser/JAM v1.19.04 (Beta   
    ON> 4.09) 19.59.17.415 : Begin 19.59.17.415 : Executing [clUnpack, clToss]   
    ON> processes. 19.59.17.420 $ New group received from 229/426@fidonet (echo   
    ON> names removed) 19.59.19.419 $ New group received from 229/426@fidonet (not   
    ON> relative to this) 19.59.40.142 $ New group received from 229/426@fidonet   
    ON> (question/post...) 19.59.52.962 * Tossed 125 PKTs, 9139 MSGs. 19.59.52.962   
    ON> : Finished.   
      
    ON> So 35 1/2 seconds to process 9,100+ msgs ... good/bad/descent?   
      
   That's hard to judge. There are so many factors of influence here.   
      
   - To how many JAM areas are these tossed?   
   - Do you have downlinks which are connected to those areas, for which new pkt   
   files are created, and maybe compressed into mail bundles?   
   - Was this done on HDD or SSD?   
   - What processor (and speed) has your computer.   
   - How much memory does your computer have, and how much is used for disk   
   caching during your toss?   
   - ...   
      
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 15/2 18/200 123/1970 154/10 203/0 221/0 226/17 229/107 354   
   SEEN-BY: 229/426 452 1014 240/5832 249/206 317 400 280/464 5003 310/31   
   SEEN-BY: 317/3 322/757 342/200 393/68 396/45 423/120 633/280 770/1   
   PATH: 280/464 229/426