Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id wACM9mAP029155 for ; Mon, 12 Nov 2018 23:09:49 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gMKJo-0004uh-IT for rs_out_1@blacksheep.org; Mon, 12 Nov 2018 22:04:28 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gMKJi-0004uU-Ue for rsgb_lf_group@blacksheep.org; Mon, 12 Nov 2018 22:04:22 +0000 Received: from rhcavuit01.kulnet.kuleuven.be ([2a02:2c40:0:c0::25:129]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91_59-0488984) (envelope-from ) id 1gMKJh-0002yU-HX for rsgb_lf_group@blacksheep.org; Mon, 12 Nov 2018 22:04:21 +0000 X-KULeuven-Envelope-From: rik.strobbe@kuleuven.be X-KULeuven-Scanned: Found to be clean X-KULeuven-ID: C1AB012032B.A2E0F X-KULeuven-Information: Katholieke Universiteit Leuven Received: from icts-p-smtps-2.cc.kuleuven.be (icts-p-smtps-2e.kulnet.kuleuven.be [134.58.240.34]) by rhcavuit01.kulnet.kuleuven.be (Postfix) with ESMTP id C1AB012032B for ; Mon, 12 Nov 2018 23:04:16 +0100 (CET) Received: from ICTS-S-EXMBX18.luna.kuleuven.be (icts-s-exmbx18.luna.kuleuven.be [10.112.11.49]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by icts-p-smtps-2.cc.kuleuven.be (Postfix) with ESMTPS id B4507200A3; Mon, 12 Nov 2018 23:04:16 +0100 (CET) Received: from ICTS-S-EXMBX27.luna.kuleuven.be (10.112.11.62) by ICTS-S-EXMBX18.luna.kuleuven.be (10.112.11.49) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 12 Nov 2018 23:04:16 +0100 Received: from ICTS-S-EXMBX27.luna.kuleuven.be ([fe80::291a:cc4f:6953:698a]) by ICTS-S-EXMBX27.luna.kuleuven.be ([fe80::291a:cc4f:6953:698a%25]) with mapi id 15.00.1395.000; Mon, 12 Nov 2018 23:04:16 +0100 X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Rik Strobbe To: "rsgb_lf_group@blacksheep.org" , "rsgb_lf_group@yahoogroups.co.uk" Thread-Topic: LF: SlowJT9 v0.9.02 Thread-Index: AQHUeqCWAdNbBbcg7k6CVkM+dmLa26VMXf0AgAArkkL///iVAIAAFYJOgAAKyZL///jsgIAAFWNA Date: Mon, 12 Nov 2018 22:04:16 +0000 Message-ID: <1542060256183.45653@kuleuven.be> References: <0ddf61c2-de83-aeef-f929-a87b698f560c@n1bug.com> <1542028810096.76526@kuleuven.be> <1542038390327.50768@kuleuven.be> <1542052074466.76606@kuleuven.be> <17488f94-c94d-a83f-f268-1fd335872b35@n1bug.com> <1542056154975.15419@kuleuven.be> <1542057189128.33390@kuleuven.be>,<56a893f6-ad99-9705-08a0-b96c509262fe@n1bug.com> In-Reply-To: <56a893f6-ad99-9705-08a0-b96c509262fe@n1bug.com> Accept-Language: nl-BE, en-GB, en-US Content-Language: nl-BE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.112.50.1] MIME-Version: 1.0 X-Spam-Score: -0.7 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Hi Paul, it seems that we will have to make a choice: - either the old JT9-2 and JT9-5 standard and only decoding one mode at a time - or keeping the current JT9-2 and JT9-5 parameters and keep the option open to decode all JT9 submodes simultanious. [...] Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [2a02:2c40:0:c0:0:0:25:129 listed in] [list.dnswl.org] -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record X-Scan-Signature: 6ffbd2c9950b634d6cc91f9565b01a8b Subject: Re: LF: SlowJT9 v0.9.02 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by klubnl.pl id wACM9mAP029155 Hi Paul, it seems that we will have to make a choice: - either the old JT9-2 and JT9-5 standard and only decoding one mode at a time - or keeping the current JT9-2 and JT9-5 parameters and keep the option open to decode all JT9 submodes simultanious. I tend to go for the second option, but everyone is welcome to convince me otherwise. 73, Rik ON7YD - OR7T ________________________________________ Van: owner-rsgb_lf_group@blacksheep.org namens N1BUG Verzonden: maandag 12 november 2018 22:43 Aan: rsgb_lf_group@blacksheep.org; rsgb_lf_group@yahoogroups.co.uk Onderwerp: Re: LF: SlowJT9 v0.9.02 I can confirm something similar. My CPU is running around 30% (it's a VERY busy system with many apps running). When SlowJT9 invokes the decoder I see a short spike to 50%, sometimes as high as 55%. 73, Paul N1BUG On 11/12/18 4:13 PM, Rik Strobbe wrote: > I just had a look at the CPU usage of my computer: > it is wobbeling between 2% and 5% but peaks to 40% if the JT9 decoder is invoked. > I am afraid that invoking 3 instances of the JT9 decoder at (almost) the same time is not a good idea. > > 73, Rik ON7YD - OR7T