Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
From: Adel Boutros <Adelboutros@live.com>
To: "users@qpid.apache.org" <users@qpid.apache.org>
Subject: [Proton-c] [0.14.0] [0.15.0] Event_loop injection is very slow
 compared to timer schedule
Thread-Topic: [Proton-c] [0.14.0] [0.15.0] Event_loop injection is very slow
 compared to timer schedule
Thread-Index: AQHSNS3ObTLWehZSoUmhI4QccQJ1Sw==
Date: Wed, 2 Nov 2016 17:28:42 +0000
Message-ID: <VI1PR0901MB0893460D30BC085A83F26DBBCDA00@VI1PR0901MB0893.eurprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [VQkzUNzrInCIO/XcpJVadBl78DuokLn1MgJLGpqadzQ=]
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1;AM5EUR02HT120;7:coYFIsGJE1VoBmSBizVJMI76/a3rS/kVc/bimFT2Ep1CNjMGGu0YSXmHBe6aPgPDJUjcm6xiQ2FOC4ktiBm9iJ8ch27X6yQBNRnvP0YdMEy1WuhFj0MGUURbAMWRHyW1Ow7fyJAIB/CZC9O4OJjrRiugJlczqEz1Qpy/HQWRKYLRu2qLo+fMGLuC16fmdrp2wECQheLUYvJEQEBnyA29rOY+uT0HSpOHnI4s2jVH5fvTCRcf4ZAqyY1tDf2/1BZHDDhvhIfeZlbtRXTAnjAPPUoht3CxpNqCKukI5tY1DygHOQ8tVqA3vmXRVtJjo/pxBB2u0jCOH6wy1Y4LIopC7exk3dxfqLX5/cldblpbcd0=
x-forefront-antispam-report: EFV:NLI;SFV:NSPM;SFS:(10019020)(98900003);DIR:OUT;SFP:1102;SCL:1;SRVR:AM5EUR02HT120;H:VI1PR0901MB0893.eurprd09.prod.outlook.com;FPR:;SPF:None;LANG:en;
x-ms-office365-filtering-correlation-id: 559712da-8381-451c-39df-08d40345b11a
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(1601124038)(1603103098)(1601125047);SRVR:AM5EUR02HT120;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(432015012)(82015046);SRVR:AM5EUR02HT120;BCL:0;PCL:0;RULEID:;SRVR:AM5EUR02HT120;
x-forefront-prvs: 0114FF88F6
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_VI1PR0901MB0893460D30BC085A83F26DBBCDA00VI1PR0901MB0893_"
MIME-Version: 1.0
X-OriginatorOrg: live.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Nov 2016 17:28:42.2853
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5EUR02HT120
X-OriginalArrivalTime: 02 Nov 2016 17:28:45.0165 (UTC) FILETIME=[9039F1D0:01D2352E]
archived-at: Wed, 02 Nov 2016 17:28:56 -0000

--_000_VI1PR0901MB0893460D30BC085A83F26DBBCDA00VI1PR0901MB0893_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,


In Proton 0.12.2, we were able to inject events from other threads to the m=
essaging_handler thread by calling timer.schedule indefinitely and queues s=
toring messages to send.


With Proton 0.14.0, We have implemented proton::thread_safe::event_loop() w=
hich should replace the above timer.schedule.


We have noticed our unit tests are 1 000 times slower with the event loop m=
echanism


We have tried having an event_loop which does nothing (Test takes 1254 mill=
iseconds instead of 4 milliseconds).


We also tried with Proton 0.15.0 but it didn't change a thing.


Are you aware of such performance regression? How can we analyze it?


Regards,

Adel


--_000_VI1PR0901MB0893460D30BC085A83F26DBBCDA00VI1PR0901MB0893_--