• testing

    From Carol Shenkenberger@1:275/100 to All on Sat Apr 20 09:53:21 2019
    h;;h
    --- SBBSecho 2.11-Win32
    * Origin: SHENK'S EXPRESS, shenks.synchro.net (1:275/100)
  • From mark lewis@1:3634/12.73 to Carol Shenkenberger on Sat Apr 20 13:43:00 2019
    On 2019 Apr 20 09:53:20, you wrote to All:

    @TZUTC: -0400
    @MSGID: 6658.asian_li@1:275/100 21209e83
    @PID: Synchronet 3.14a-Win32 Dec 31 2006 MSC 1200
    @TID: SBBSecho 2.11-Win32 r1.182 Dec 31 2006 MSC 1200
    h;;h
    --- SBBSecho 2.11-Win32
    * Origin: SHENK'S EXPRESS, shenks.synchro.net (1:275/100)
    SEEN-BY: 15/0 19/36 34/999 90/1 104/57 106/201 116/18 123/140 153/7715 218/700
    SEEN-BY: 222/2 230/150 152 240/1120 250/1 261/38 100 1466 266/512 267/155 SEEN-BY: 275/0 89 90 91 93 95 96 98 100 201 362 282/1031 1056 291/1 111 SEEN-BY: 320/119 219 340/400 342/13 396/45 712/848 801/161 189 2320/105 SEEN-BY: 3634/12 5020/715 1042 116/116 123/25 150 755 135/300 154/10 3634/15
    SEEN-BY: 3634/27 50 123/50 115 3634/0 18/0 123/0 1/120
    @PATH: 275/100 261/38 3634/12



    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... PregNet: Undergoing rapid expansion!
    ---
    * Origin: (1:3634/12.73)
  • From Ozz Nixon@1:1/123 to mark lewis on Sat Apr 20 15:33:12 2019
    Real Question: ^aCHRS: CP437 2 vs ^aCHRS: IBMPC 2

    Is there a difference? (I thought those both imply the same...)

    --
    .. Ozz Nixon
    ... Author ExchangeBBS (suite)
    .... Since 1983 BBS Developer

    --- ExchangeBBS NNTP Server v3.1/Linux64
    * Origin: (1:1/123)
  • From mark lewis@1:3634/12.73 to Ozz Nixon on Sun Apr 21 06:00:34 2019
    On 2019 Apr 20 15:33:12, you wrote to me:

    Real Question: ^aCHRS: CP437 2 vs ^aCHRS: IBMPC 2

    Is there a difference? (I thought those both imply the same...)

    AFAIK, they're the same... one is obsolete, though...

    http://ftsc.org/docs/fts-5003.001

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Beware the do-gooders. They'll screw it up with best of intentions.
    ---
    * Origin: (1:3634/12.73)
  • From Ozz Nixon@1:1/123 to Ozz Nixon on Tue Apr 23 01:30:38 2019
    On 2019-04-23 00:37:51 +0000, Ozz Nixon -> mark lewis said:

    On 2019-04-21 06:00:34 +0000, mark lewis -> Ozz Nixon said:


    )\/(ark

    Added a couple more variables and ran the gated USENET feed for the day:

    21.09.39.342 * Tossed 824 PKTs, 63271 MSGs, 3 MSGs to Ozz Nixon
    21.09.39.342 * Summary processed 180599194 bytes in 234 seconds.
    21.09.39.342 * Speed 771791 bytes read a sec. 270 msgs a second.
    21.09.39.342 * Speed 459980 bytes written a sec. 107635526 bytes written.

    * Variance in Read vs Write totals is - I do not store SEEN-BY in the BBS.

    --- ExchangeBBS NNTP Server v3.1/Linux64
    * Origin: (1:1/123)
  • From Ozz Nixon@1:1/123 to mark lewis on Tue Apr 23 00:37:51 2019
    On 2019-04-21 06:00:34 +0000, mark lewis -> Ozz Nixon said:


    )\/(ark


    A while back you had mentioned it took around 30m to process a lot of
    mail on your system. I am now focusing on tweaking the what I have
    implemented JAMmb and my PKT parser... current stats from log:

    ------------ Mon 22 Apr 19 ExchangeBBS FTN Tosser/JAM v1.19.04 (Beta 4.09) 19.59.17.415 : Begin
    19.59.17.415 : Executing [clUnpack, clToss] processes.
    19.59.17.420 $ New group received from 229/426@fidonet (echo names removed) 19.59.19.419 $ New group received from 229/426@fidonet (not relative to this) 19.59.40.142 $ New group received from 229/426@fidonet (question/post...) 19.59.52.962 * Tossed 125 PKTs, 9139 MSGs.
    19.59.52.962 : Finished.

    So 35 1/2 seconds to process 9,100+ msgs ... good/bad/descent?

    --- ExchangeBBS NNTP Server v3.1/Linux64
    * Origin: (1:1/123)
  • From Wilfred van Velzen@2:280/464 to Ozz Nixon on Tue Apr 23 14:37:03 2019
    Hi Ozz,

    On 2019-04-23 00:37:51, you wrote to mark lewis:

    A while back you had mentioned it took around 30m to process a lot of
    mail on your system. I am now focusing on tweaking the what I have implemented JAMmb and my PKT parser... current stats from log:

    ------------ Mon 22 Apr 19 ExchangeBBS FTN Tosser/JAM v1.19.04 (Beta 4.09) 19.59.17.415 : Begin 19.59.17.415 : Executing [clUnpack, clToss] processes. 19.59.17.420 $ New group received from 229/426@fidonet (echo names removed) 19.59.19.419 $ New group received from 229/426@fidonet (not relative to this) 19.59.40.142 $ New group received from 229/426@fidonet (question/post...) 19.59.52.962 * Tossed 125 PKTs, 9139 MSGs. 19.59.52.962 : Finished.

    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)
  • From mark lewis@1:3634/12.73 to Ozz Nixon on Tue Apr 23 10:45:04 2019
    On 2019 Apr 23 00:37:50, you wrote to me:

    A while back you had mentioned it took around 30m to process a lot of
    mail on your system.

    that was due to the age of the system and possibly some file system fragmentation from dwindling drive space across 6 drives...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... A member of CCAC (Concerned Citizens Against Cilantro)
    ---
    * Origin: (1:3634/12.73)
  • From mark lewis@1:3634/12.73 to Wilfred van Velzen on Tue Apr 23 10:47:10 2019
    On 2019 Apr 23 14:37:02, you wrote to Ozz Nixon:

    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.

    that's true... also, "are there any shortcuts being taken" comes to mind... eg:
    zeroing seconds in the time stamps...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Outside of dogs, books are best friends. Inside dogs, too dark to read.
    ---
    * Origin: (1:3634/12.73)
  • From Carol Shenkenberger@1:275/100 to mark lewis on Sun Apr 21 11:56:48 2019
    Re: testing
    By: mark lewis to Carol Shenkenberger on Sat Apr 20 2019 01:43 pm

    Thanks Mark!

    I crashed Monday early in the morning and for once, it took 6 days to get back online. A combination of heavy work load (had only a 2 hour slice during the week) and some unusual (to me) issues that had to do with a mis-installed factory XP.

    Gotta love it! I'd accicdently gifted off my last copy of XP-Pro thinking I had another. oops. One on order but won't arrive til next week (along with another spare XP box).

    I was up for all but outbound fidonet by Thursday. # was the issue (but it's got others I have not narrowed in as of yet. What I see is a 'number pound' when I type a backslash. Messed with environment variables. Several other special characters mucked with. Anyways, once I figured out what the driver was, I had to edit a bunch of stuff around it. Came up Sat morning.

    xxcarol
    --- SBBSecho 2.11-Win32
    * Origin: SHENK'S EXPRESS, shenks.synchro.net (1:275/100)
  • From Ozz Nixon@1:1/123 to mark lewis on Mon Apr 29 09:22:51 2019
    On 2019-04-23 10:47:10 +0000, mark lewis -> Wilfred van Velzen said:

    On 2019 Apr 23 14:37:02, you wrote to Ozz Nixon:

    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.

    that's true... also, "are there any shortcuts being taken" comes to mind... eg: zeroing seconds in the time stamps...

    I understand shortcuts, none, not even buffering techniques... it is
    raw read/parse/write to JAM and the log. The log is probably the most sophisticated part of the whole tosser, deciding where, what, when to
    log... so it is useful, without being a dump of the PKT itself.

    I was just cursious if I should spend time to make it faster -
    prefetching PKT bytes, buffering the log and JAM files. But, I like it
    having as small of a foot print, and the fact it is interpreted instead
    of native binary.

    Thanks for feedback(s)...
    O.

    --- ExchangeBBS NNTP Server v3.1/Linux64
    * Origin: (1:1/123)